I just did this method on one of my friends machine and installed Windows 7 and Windows 8 . The main advantage is that by using USB drive you will be able to install Windows 7 or Windows 8 in just 15 minutes. You can also use this bootable USB drive on friend’s computer who doesn’t have a DVD optical drive.

The method is very simple and you can use without any hassles. Needless to say that your motherboard should support USB Boot feature to make use of the bootable USB drive.

Requirements:

*USB Flash Drive (Minimum 4GB)

*Windows 7 or Windows 8 installation files.

Follow the below steps to create bootable Windows 7/Windows 8 USB drive using which you can install Windows 7 or Windows 8 easily.

Procedure:

1. Plug-in your USB flash drive to USB port and move all the contents from USB drive to a safe location on your system.

2. Open Command Prompt with admin rights. Use any of the below methods to open Command Prompt with admin rights.

*Type cmd in Start menu search box and hit Ctrl+ Shift+ Enter.

Or

*Go to Start menu > All programs > Accessories, right click on Command Prompt and select Run as administrator.

3. You need to know about the USB drive a little bit. Type in the following commands in the command prompt:

First type DISKPART and hit enter to see the below message.

Next type LIST DISK command and note down the Disk number (ex: Disk 1) of your USB flash drive. In the below screenshot my Flash Drive Disk no is Disk 1.

4. Next type all the below commands one by one. Here I assume that your disk drive no is “Disk 1”.If you have Disk 2 as your USB flash drive then use Disk 2.Refer the above step to confirm it.

So below are the commands you need to type and execute one by one:

SELECT DISK 1

CLEAN

CREATE PARTITION PRIMARY

SELECT PARTITION 1

ACTIVE

FORMAT FS=NTFS

(Format process may take few seconds)

ASSIGN

EXIT

Don’t close the command prompt as we need to execute one more command at the next step. Just minimize it.

5. Next insert your Windows7/Windows 8 DVD into the optical drive and check the drive letter of the DVD drive. In this guide I will assume that your DVD drive letter is “D” and USB drive letter is “H” (open my computer to know about it).

6. Maximize the minimized Command Prompt in the 4th step.Type  the following command now:

D: CD BOOT and hit enter.Where “D” is your DVD drive letter.

CD BOOT and hit enter to see the below message.

7. Type another command given below to update the USB drive with BOOTMGR compatible code.

BOOTSECT.EXE /NT60 H:

Where “H” is your USB drive letter. Once you enter the above command you will see the below message.

8. Copy your Windows 7 or Windows 8 DVD contents to the USB flash drive.

9. Your USB drive is ready to boot and install Windows 7 or Windows 8. Only thing you need to change the boot priority at the BIOS to USB from the HDD or CD ROM drive. I won’t explain it as it’s just the matter the changing the boot priority or enabling the USB boot option in the BIOS.

Note: If you are not able to boot after following this guide means you haven’t set the BIOS priority to USB. If you got any problem in following this guide feel free to ask questions by leaving comment.

Update: If you find this guide difficult to follow, please use the easy-to-use guide to create a bootable USB to install Windows 7  or Windows 8 using official tool.

Features

BES Express is based on the BES 5.0.1 MR1 code, and as such offers much (but not all) of the same functionality:

• Web-based administration
• 6 pre-defined administrative roles
• BlackBerry Web Desktop
• Over 35 IT policies for device management (see below), including device wipe
• HTML email support
• Flag emails for follow-up
• Mail folder management
• Remote email search
• Set out of office status and message
• Forward calendar appointments
• Open attachments in calendar appointments
• Free / Busy lookup
• Remote file access
• Support for audio (AWE, WAV, MP3, WMA) files

The following features are NOT available in BES Express:

• Cradle-less enterprise activation (when used with the BIS tariff on client devices)
• Ability to define multiple administrative roles
• BlackBerry Monitoring Service
• BlackBerry Enterprise Transporter Tool
• High Availability deployment options
• Support for BlackBerry Mobile Voice System (MVS)
• Support for enterprise instant messaging and social networking integration

At the time of writing, BES Express is only available in English.
BES Express is not compatible with Lotus Domino or Novell Groupwise installations.

System Requirements

Operating System

• Windows Server 2003 SP2 (32-bit or 64-bit)
• Windows Server 2003 R2 SP2 (32-bit or 4-bit)
• Windows Server 2008 SP2 (32-bit or 64-bit)
• Windows Small Business Server 2003
• Windows Small Business Server 2008

Microsoft Exchange Messaging Server

• Microsoft Exchange 2003 SP2
• Microsoft Exchange 2007 SP1
• Microsoft Exchange 2010 including Update Rollup 1

Microsoft Exchange System Tools

• (Exchange 2003) Microsoft Exchange 2003 SP2 System Manager or MAPI client and CDO 1.2.1 version 6.5.8039.0 or later
• (Exchange 2007) MAPI client and CDO 1.2.1 version 6.5.8067.0 or later
• (Exchange 2010) MAPI client and CDO 1.2.1 version 6.5.8146.0 or later

Hardware

(Up to 200 users)
• Single processor, 2.0GHz Intel Xeon (2 processors recommended)
• 2GB memory
• 2 HDDs, RAID 1

  (Up to 500 users)

• Two processors, 2.0GHz Intel Xeon
• 2GB memory
• 2 HDDs, RAID 1

  (Up to 1000 users)

• Two processors, 2.0GHz Intel Xeon
• 3GB memory
• 2 HDDs, RAID 1

Database

Any of the following database management systems are supported:

• MSDE 2000 SP3
• Microsoft SQL Server 2005 SP3 (32-bit or 64-bit)
• Microsoft SQL Server 2005 Express Edition SP3
• Microsoft SQL Server 2008 SP1 (32-bit or 64-bit)
• Microsoft SQL Server 2008 Express Edition SP1 (32-bit or 64-bit)

If using a database system earlier than SQL 2005 SP3, the following hotfix should be installed on the database server – http://support.microsoft.com/?kbid=960082

Miscellaneous

In order to provide support for audio attachments, Windows Media Player 9 or later is required on the BES.

Internet Explorer 6 or later is required to access the web administration console.

Firewall

The BES requires outbound-initiated, bi-directional access to the Internet on TCP port 3101 as well as access to DNS.

RIM recommend operating up to a maximum of 75 users if the BES Express software is being installed directly onto the Exchange server itself. On a standalone server, BES Express can support up to 2,000 users. Multiple BES Express servers can be deployed in the same BlackBerry domain.

Preparing an Exchange 2010 environment

NOTE – this article assumes an Exchange 2010 installation only. Visit the BES Express section of the blog for details on installing the solution against Exchange 2003 or 2007.

Ensure that Exchange 2010 Update Rollup 1 is installed on the Exchange 2010 server. This package is available here – http://www.microsoft.com/downloads/details.aspx?FamilyID=371add31-d7a0-4…

If installing the BES Express software on the Exchange server itself, the Exchange server should NOT itself also be a domain controller.

Create a domain user account called BesAdmin

On the Exchange server, in the Active Directory Users and Computers console, create a domain user called “BesAdmin” and assign it an Exchange mailbox. Set the user account password to never expire.

Send an email to the BesAdmin user to initialise the Exchange mailbox.

Assign the BesAdmin user local administrative rights

On the server that is to host the BES Express, make the BesAdmin domain user a member of the local administrator group. NOTE – the BES Express server will first need to have been added to the Domain if not done already.
To do this, on the BES Express server, right click on the icon for My Computer and select Manage. Browse to Local Users and Groups –> Groups –> Administrators and add the BesAdmin user:

Assign the BesAdmin user “log on as a service” rights

On the BES Express server, also assign the BesAdmin domain user account “log on as a service” rights. To do this, select Administrative Tools –> Local Security Policy –> User Rights Assignment –> Log on as a service and add the BesAdmin user:

Assign “Receive As” and “Administer Information Store” rights to the BesAdmin user

On the Exchange server, launch the Exchange PowerShell and issue the following command:

Get-MailboxDatabase | Add-ADPermission -User "BesAdmin" -AccessRights
 ExtendedRight -ExtendedRights Receive-As, ms-Exch-Store-Admin

Assign Exchange View-Only Administrator rights to the BesAdmin user

Still within the Exchange PowerShell, now issue the following command:

Add -RoleGroupMember "View-Only Organization Management" -Member "BesAdmin"

Assign “Send As” rights on the domain to the BesAdmin user

Within the Active Directory Users and Computers console, open the View menu and select the option to display Advanced Features.

Right click on the domain and select Properties. Click on the Security tab:

Click on the Advanced button:

Click on Add and type in the name of the BesAdmin user:

Select the option to Apply Onto User Objects.
Scroll down to the bottom and tick the option to enable Send As rights:

For good measure, also enable Send As rights on the Exchange server itself within the Exchange PowerShell. Launch the console and issue the following command:

Add-ADPermission -InheritedObjectType User -InheritanceType Descendents -ExtendedRights
Send-As -User "BesAdmin" -Identity "CN=Users,DC=domain,DC=com"

(where “domain” and “com” should be substituted for your specific domain details, eg: DC=brightpoint,DC=co,DC=uk and so on)

To force all of the above changes to take effect on the domain, it may be worth running a group policy update. On the Exchange server click Start –> Run and issue the command “gpupdate /force”

Turn off Exchange 2010 Client Throttling

Exchange 2010 uses client throttling by default to protect the Exchange server from excessive user demands. RIM recommend turning off this feature as it can have an adverse affect on the performance of the BES solution. This is done within the Exchange PowerShell console.
Launch the console and issue the following command to get the “Identity” of the default throttling policy”

Get-ThrottlingPolicy | Where-Object {$_.IsDefault -eq "True"} | FL Identity

the Identity will be displayed:

Now issue the following command:

Set-ThrottlingPolicy -RCAMaxConcurrency $null

You will be prompted to enter the Identity to apply the policy to, enter the result returned above:

Increase the maximum number of connections to the Exchange Address Book Service

On the Exchange Server (or specifically the Client Access Server in a multi-box deployment), browse to C:\Program Files\Microsoft\Exchange Server\V14\Bin and locate the file “microsoft.exchange.addressbook.service.exe.config” and open it in NotePad:

Locate the line “MaxSessionsPerUser”:

Increase the value to 100000. Save the file then restart the Address Book Service:

Install the Exchange MAPI CDO 1.2.1 package

The Microsoft Exchange MAPI CDO 1.2.1 package must be installed to provide the BesAdmin user a MAPI connection to Exchange mailboxes as well as access to calendaring information. This package is available for download from our FTP site HERE (Exchange 2010 only).

Run the installer and accept the license agreement:

Now you’re ready to install the BES Express software.

Installing the BlackBerry Enterprise Server Express software

LOG INTO THE BES EXPRESS SERVER AS THE BESADMIN USER!

Launch the BES Express installer, you will be prompted to confirm that you are indeed logged in as the correct user:

Click Continue Installation:

Choose your country and read the license agreement. Select the option to accept if you agree to the terms and conditions:

Select the option to Create a BlackBerry Configuration Database:

Select the option to install a BlackBerry Enterprise Server:

Verify that all pre-requisite checks are completed successfully, paying attention to any warnings or failures:

In this article I am allowing the BES Express installer to install a local copy of SQL Server Express, if you intend to use a dedicated SQL Server, select this option and enter the details of the server address:

Enter the password for the BesAdmin account and enter in a name for the BES Express server: this name can be a ‘friendly’ one and is used to identify it in the Web Administration interface:

If you are warned that the server does not have sufficient free disk space available, free up some space before continuing:

A summary of the installation options will be displayed:

Click Install, the required components will now be installed, this process may take a while. When complete you will be prompted to reboot the server:

Click Yes. Once rebooted, log back in as the BesAdmin user. The installation will resume automatically:

Enter a name for the Configuration Database – this should ideally be left at the default unless specifically required. Click Next:

You will be prompted to create the database, click Yes:

When created, click OK:

Enter in the 10,000-user CAL, SRP key and SRP authentification key you were supplied along with the BES Express download. Verify connectivity to the RIM Relay on TCP port 3101. Click Next:

The MAPI connection settings will now be required, enter in the name of the Exchange server as well as the BesAdmin user account mailbox. Click OK:

Enter in the name you wish to use for the Administration web site. Again this should be left at the default if you are unsure as to what this means. Any name you choose should be resolvable via DNS if not using the default option.
Enter in a password for the SSL certificate – this is generated automatically by the installer and assigned to the Apache-based administration web site (the site does not run within IIS). The certificate is generated based on the name entered.
By default the administration web site runs on port 3443 – this can be altered if desired but again leave this value at the default unless specifically required. Click Next:

Enter in the details of the BesAdmin user account again and click Next:

Specify whether you wish access to the administration web site to be authenticated based on Active Directory credentials, or whether you want to use the built-in BlackBerry Administration Service authentication. If you select the second option, enter in a password for the default admin account.

NOTE – if you select BlackBerry Administration Service authentication, the default admin username is “ADMIN”, NOT “BESADMIN”.

Click Next:

Select the option to Start Services and verify that all services start successfully:

Click Next:

You will be reminded what the address is to access the administration web site. Click Finish.

The software is now installed and ready to use. To access the web administration site, a link will have been added to the Programs folder on the Start menu:

Selecting the link will launch the default browser on the server (which needs to be Internet Explorer 6 or later):

Log in ether as the BesAdmin user (using Windows authentication) or as the Admin user (using BlackBerry authentication):

Add the web site to the Trusted Sites group in the Internet Explorer security options area:

And add the web site certificate to the trusted certificate authority folder:

Adding Users

In the Administration web site, select the option to Create a user:

Selecting Search will display a list of all available users:

Tick the user(s) you want to add and click Continue:

Select the BES Server the users should be added to (you’ll only have one option) and click Next. The users will now be added to the BES Server.

To associate a device to a user, the BlackBerry handheld itself can be connected directly to the BES Express server via USB. In the Administration web site browse to Devices –> Attached Devices –> Overview:

When the device is connected, its PIN details will be displayed:

Select the option to Assign current device to a user. Select the user you want to associate the device with:

The device will now be associated to the user and will automatically activate itself and begin to download user mailbox data.

Troubleshooting

If you encounter any problems adding or activating users, first verify that all BlackBerry services have started and are running correctly:

Exchange Permissions

The commonest cause of problems when troubleshooting issues with a BES installation is that the correct permissions have not been assigned to the BesAdmin user on the domain and the Exchange server as detailed above.
Included with the BES Express software is a utility called “IEMSTEST” which can verify the BesAdmin user’s access to specific user mailboxes.

The utility lives in the C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility folder and needs to be run at the command line:

Select the BlackBerryServer MAPI profile when prompted:

Select the user account you wish to query:

The permissions will be tested:

As you can see from the above screenshot this test has indicated that the BesAdmin account does not have Send As rights on my James Liddiard user account. Once I verify my permissions, re-running the test indicates that all test have passed successfully:

Double-clicking the MSI file launches a standard Windowsinstallation routine. When the installation process completes, the IIS 6.0Migration Tool is installed into the C:\Program Files\IIS Resources\IIS 6.0Migration Tool 1.1 folder. The actual migration tool is named iismt.exe. Thesyntax is as follows:

iismt <server> <website> [/user <username>[/password <password>]
[/path <path>][/serverbindings <serverbindings string>]
[/siteid <<siteID> |replace>] [/configonly] [/fpse] [/inherited]
[/verbose]

Switches for this command are:

• <server>ï¿?thename of your IIS 4.0 server.
• <website>ï¿?the name or metabasepath of the Web site you’re migrating.
• /user <username>ï¿?the usernameof the user you want to perform the operation.
• /password <password>ï¿?the passwordfor the corresponding user account.
• /path <path>ï¿?the path to theWeb root folder.
• /serverbindings <serverbindings>ï¿?theIP address and port number to be used by the server as a binding (IP:Port:Hostname).
• /siteid <<siteid> |replace>ï¿?the number of the Web site you are migrating. You may specify anumeric value to use as the site ID, or specify the keyword “replace”to use the existing siteID.
• /configonlyï¿?migrate IIS configuration only.
• /fpseï¿?re-extendFrontPage Server-extended Web sites.
• /verboseï¿?Verbose mode.
• /overwriteï¿?suppressesprompting to confirm that you want to overwrite an existing destination folderor file.
• /noninteractiveï¿?does not display messages that prompt theuser for input. Program will exit on first error condition.

Some examples of how to use the IISMT command are asfollows:

ï¿?ï¿?ï¿?

ï¿? iismt Server1"My Web Site" /user Administrator /password pass /pathd:\inetpub\wwwroot

iismt Server1 w3svc/3 /path d:\MigratedWebs /fpse /serverbindings147.100.100.34:80:www.brienposey.com

The IIS 6.0 Migration Tool does a great job of migratingsimple Web sites that are accessed only anonymously. If your Website is more complex, you may still find the tool useful, but there will be alot of manual work you’ll have to do once the migration is complete.

There is a need to move Symantec Endpoint Protection Manager (SEPM) from the machine where it is currently installed (MACHINE_1) to another (MACHINE_2).

Environment

There are two different situations:

(1) MACHINE_2 will have the same IP address and/or hostname as MACHINE_1

(2) MACHINE_2 will have an IP address and hostname which are different from MACHINE_1

Solution

There are two solutions available, with their advantages and drawbacks:

(A) Replication: this is a faster solution to implement. However, this solution will be appropriate for situation 2 only (see Environment section above).

(B) Disaster Recovery: this solution is longer to implement but the new SEPM will be an exact copy of the current one. This solution will be appropriate for both situation 1 and 2 (see Environment section above).

IMPORTANT NOTE: SEPM installed on MACHINE_2 must be the same version as on MACHINE_1 (same release and same language)

1) MACHINE_2 will have at least either same IP or hostname as MACHINE_1

Disaster Recovery method

Follow “Best Practices for Disaster Recovery with Symantec Endpoint Protection” (see Related Articles below).

Symantec Endpoint Protection clients will be able to reach the new SEPM using either unchanged IP or hostname. Management server list will then be updated accordingly and sent automatically to clients.

2) MACHINE_2 will have both IP and hostname different from MACHINE_1

A) Replication method

1.Install Symantec Endpoint Protection Manager on MACHINE_2
NOTE: The version installed to the new server must be the same version as on the old server. The new management console can be migrated to a newer version once the transition is complete.
2.In the Management Server Configuration Wizard panel, check Install an additional site, and then click Next
3.In the Server Information panel, accept or change the default values for the following boxes, and then click Next

•Server Name
•Server Port
•Server Data Folder
4.In the Site Information panel, accept or change the name in the Site Name box, and then click Next
5.In the Replication Information panel, type values in the following boxes:
•Replication Server Name
The Name or IP address of MACHINE_1
•Replication Server Port
The default is 8443.
•Administrator Name
The Username used to log on to the old console.
•Password
The password used to log on to the old console.
6.Click Next
7.In the Certificate Warning dialog box, click Yes
8.In the Database Server Choice panel, do one of the following, and then click Next:
Check Embedded database or Microsoft SQL server (whichever database type you’d prefer to install), then complete the installation.
9.Log in to the new SEPM on MACHINE_2 and ensure that all the clients and policies have Migrated successfully.
10.Click Policies > Policy Components > Management Server Lists > Add Management Server List
11.Click Add> Priority and a new Priority would get added named as “Priority2″
12.Add MACHINE_1 under Priority 2 and add MACHINE_2 under Priority 1, and assign this New Management Server List to all the groups.
13.Wait at least one replication cycle.
14.Stop the “Symantec Endpoint Protection Manager” and “Symantec Embedded Database” service on MACHINE_1 to verify whether all clients now report to the new SEPM on MACHINE_2
15.Once verified that all the clients are reporting into the new SEPM, and have moved away from the old one, proceed to the next step.
16.Delete the Replication Partner from MACHINE_2 SEPM: Click on the Admin button | Under View Servers, Expand Replication Partners and select the partner to delete | Under Tasks, choose Delete Replication Partner | Type Yes when asked to verify deletion of the replication partner.
17.After the successful Migration, uninstall SEPM from MACHINE_1

B) Disaster Recovery method

1.Follow “Best Practices for Disaster Recovery with Symantec Endpoint Protection” (see Related Articles below) to backup and reinstall SEPM on MACHINE_2
2.Log in to the old SEPM on MACHINE_1
3.Click Policies > Policy Components > Management Server Lists > Add Management Server List
4.Click Add> Priority and a new Priority would get added named as “Priority2″
5.Add MACHINE_1 under Priority 2 and add MACHINE_2 under Priority 1, and assign this New Management Server List to all the groups.
6.Clients will then move from old SEPM to new one gradually
7.Stop the “Symantec Endpoint Protection Manager” and “Symantec Embedded Database” service on MACHINE_1 to verify whether all client now report to the new SEPM on MACHINE_2
8.Once verified that all the clients are reporting into the new SEPM, and have moved away from the old one, proceed to the next step.
9.Uninstall SEPM from MACHINE_1

Dim SmtpServer

Dim EmailSender, EmailRecipient, EmailSubject

Dim aFile

Dim fNewest, fNewestZipped

Dim oFolder

Dim LogFolder

Dim numFiles

Dim Compress, CompressExe

Dim EmailClient

‘ Set your preferences here *

SmtpServer                = “ex2010.uk.itaction.net”

EmailSender                = “sandip.patel@itaction.in“

EmailRecipient        = “indianoc@itaction.in“

EmailSubject        = “NTBackup Log File”

LogFolder                = “C:\Documents and Settings\sgpatel\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data”

Compress                = 0        ‘ Set to 1 if you have Winzip installed

CompressExe                = “C:\Program Files\Winzip\wzzip”

EmailClient                = “C:\Blate\blat.exe”

Set WshShell        = WScript.CreateObject(“WScript.Shell”)

Set oFolder                = CreateObject(“Scripting.FileSystemObject”).GetFolder(LogFolder)

numFiles = 0

‘ Find log file with latest time stamp

For Each aFile In oFolder.Files

       If Right(aFile.Name, 4) = “.log” Then

               numFiles = numFiles + 1

               If fNewest = “” or fNewest = null Then

                       Set fNewest = aFile

               Else

                       If fNewest.DateLastModified < aFile.DateLastModified Then

                               Set fNewest = aFile

                       End If

               End If

       End If

Next

‘ Only compress if configured to do so

If Compress = 1 Then

       fNewestZipped = fNewest & “.zip”

Else

       fNewestZipped = fNewest

End If

‘ Email log file

If numFiles > 0 Then

       If Compress = 1 Then

               CommandLine = “”"” & CompressExe & “”" -u “”" & fNewestZipped & “”" “”" & LogFolder & “\” & fNewest.Name & “”"”

               WshShell.Run CommandLine, 3, 1

       End If

       WshShell.Run EmailClient & ” – -body “”NTBackup Log File”" -attach “”" & fNewestZipped & “”" -server ” & SmtpServer & ” -f ” & EmailSender & ” -subject ” & chr(34) & EmailSubject & chr(34) & ” -to ” & EmailRecipient, 3, 1

End If

Exchange 2010, Windows 2008 SP2, English, 64bit

Exchange 2010, Windows 2008 R2, English, 64 bit

PROBLEM:

Exchange 2010 setup does detailed check on prerequisites, but does not install them for you. You are expected to  manually install and configure all required hotfixes, server components and services which is inefficient and time consuming.
SOLUTION:  

Use one of the batch files provided below. The batch file takes care of everything (installs hotfixes, enables required services, installs Windows server components, reboots the server)  and is optimized to do everything in a single pass with a single reboot (if required).

Two variations of the batch files are provided:

a) ex2010.bat - this one will present you with menu options and allow you to select individually for which Exchange roles you would like prerequisites to be installed (for example just for mailbox role).

b) ex2010turbo.bat – this one is a “full auto” script which installs all the prerequisites for all Exchange roles without any input required from the user. Start it, go for a coffee, and by the time you are back your server is restarted with everything installed on it, ready for Exchange 2010 to be deployed. 
Prerequisites are different for Windows 2008 SP2  and Windows 2008 R2, so please make sure you use correct version of the scripts and updates.
The batch files are available for download as an ISO image file or a ZIP file .

http://www.exchangemaster.net/index.php?option=com_content&task=view&id=98&Itemid=1&lang=en

1. - Get-ExchangeCertificate -DomainName server.yourdomain.com
2. - (copy the thumbprint of the expired SSL)
3. - Get-ExchangeCertificate -Thumbprint <expired SSL thumbprint> | New-ExchangeCertificate
4. - Get-ExchangeCertificate -DomainName server.yourdomain.com
5. - (copy the thumbprint of the ”new” SSL)
6. - Enable-ExchangeCertificate <New SSL thumprint> -Services:”IIS”