The result is that I cannot change any drivers or devices.

The solution is very simple but not obvious. My computer name is longer than 15 characters. This is a problem for NetBIOS computers. It turns out this is also a problem for the device manager. So I changed my computer name to a name with less than 15 characters, now everything works normal again.

The first one I tried in my own lab was the one that Daniel Petri describes in het Blog post at: http://www.petri.co.il/reset_domain_admin_password_in_windows_server_2003_ad.htm

There were some requirements for this trick.

• Local access to the domain controller (DC).
• The Local Administrator password.
• Two tools provided by Microsoft in their Resource Kit: SRVANY and INSTSRV. Download them from HERE (24kb).

The first one was no problem, but the second one in my case was a problem, we didn’t no the local administrator password.

So this is how I did it, first of all download the DART tools (Diagnostics and Recovery Toolset) from the Microsoft website, this is available for MDOP License owners. See http://www.microsoft.com/windows/enterprise/products/mdop/dart.aspx

There are other ways to get your hands on this tool, go to the Technet site and get a Technet Subscription. And if you don’t have access to both sources, go search Google.

I restarted the domain domain controller, and boot into the DART tool. Go to the Locksmith tool, and reset the password of the Administator account. Reboot the server, in Active Directory Recovery mode. This is important because now the Local accounts are available for logon. The local accounts are disabled on a Domain Controller, this is by design. In recovery mode logon with your new local Administrator password. Now do the trick that Daniel Petri describes in his post.

This is how it works globally.

Step 1

Restart Windows 2003 in Directory Service Restore Mode.

Note: At startup, press F8 and choose Directory Service Restore Mode. It disables Active Directory. When the login screen appears, log on as Local Administrator. You now have full access to the computer resources, but you cannot make any changes to Active Directory.

Step 2

You are now going to install SRVANY. This utility can virtually run any programs as a service. The interesting point is that the program will have SYSTEM privileges (LSA) (as it inherits the SRVANY security descriptor), i.e. it will have full access on the system. That is more than enough to reset a Domain Admin password. You will configure SRVANY to start the command prompt (which will run the ‘net user’ command).

Copy SRVANY and INSTSRV to a temporary folder, mine is called D:\temp. Copy cmd.exe to this folder too (cmd.exe is the command prompt, usually located at %WINDIR%\System32).

Start a command prompt, point to d:\temp (or whatever you call it), and type:

instsrv PassRecovery "d:\temp\srvany.exe"

(change the path to suit your own).

It is now time to configure SRVANY.

Start Regedit, and navigate to

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\PassRecovery

Create a new subkey called Parameters and add two new values:

name: Application

type: REG_SZ (string)

value: d:\temp\cmd.exe

name: AppParameters

type: REG_SZ (string)

value: /k net user administrator 123456 /domain

Replace 123456 with the password you want. Keep in my mind that the default domain policy require complex passwords (including digits, respecting a minimal length etc) so unless you’ve changed the default domain policy use a complex password such as P@ssw0rd

Now open the Services applet (Control Panel\Administrative Tools\Services) and open the PassRecovery property tab. Check the starting mode is set to Automatic.

Go to the Log On tab and enable the option Allow service to interact with the desktop.

Restart Windows normally, SRVANY will run the NET USER command and reset the domain admin password.

Step 3

Log on with the Administrator’s account and the password you’ve set in step #2.

Use this command prompt to uninstall SRVANY (do not forget to do it!) by typing:

net stop PassRecovery

sc delete PassRecovery

Now delete d:\temp and change the admin password if you fancy.

Done!

Test Lab Guides

This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010.

For this migration to work you will need the following software:

Steps required:

It’s important that the steps are followed in order as different stages make different changes to the way in which your server operates.  For example you MUST make the 2008 server a domain controller before you install Exchange.

Step 1 – Health Checks on Small Business Server 2003

The absolute first thing you need to do is take a SYSTEM STATE backup of your Small Business Server as well as a full system backup.  There is little chance of the data getting lost but the SYSTEM STATE backup backs up Active Directory so that if it all goes wrong we can recover it if needed.

What you then need to do on the SBS 2003 server is to make sure you have all the latest available updates.  This means you should at a minimum have:

Once you have installed all of the above, run Windows Update and make sure you select the option in the blue banner bar across the top for Microsoft Update.  Microsoft Update will then allow you to update all Microsoft products installed on the server providing a more comprehensive update solution.  Keep running the check and installing all updates until there are no more available.

Check the health of your Active Directory by running DCDIAG, if there is anything reported as an error fix it before moving on.

Run the Small Business Server 2003 Best Practices Analyser from here:  http://www.microsoft.com/downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

Make sure you fix any problems the analyser identifies. If you cannot, then why not raise a question on EE to have our Experts help you?

A common problem that can cause this migration to fail is that the SBS 2003 server does not have its own IP address listed for DNS in the network properties under TCP/IP.  If this is the case, update it so that it does (do not use the loopback 127.0.0.1 address).

Step 2 – Join new Windows 2008 Server to the domain as a member server

To join a Windows 2008 Server to the Small Business Server domain we need to first ensure that it is receiving a correct IP Address

Allow the Windows 2008 Server to receive a DHCP Address from your Small Business Server.  Run an IPCONFIG /ALL to check this.  The DNS Server entry is probably the most important. This should be configured to use the IP Address of your Small Business Server for DNS.

To test, it might be worth just pinging the SBS 2003 server from a command prompt just to check the name can be resolved by doing the following:

If you get a good response then we can try and join the 2008 server to the domain.

To Join the Server to the Domain, do the following:

Step 3 – Prepare Active Directory for Windows 2008 R2 Server

The first step of this process is to raise the Functional Levels of the SBS 2003 server.  This involves raising the domain and forest functional level of Active Directory and the Operational mode of Exchange Server.

To raise the Domain Functional Level do the following:

To raise the Forest Functional Level do the following:

And we also need to raise the Exchange Operational Mode.  To do this, you need to do the following:

Before we can add the Windows 2008 Server as a domain controller to the SBS 2003 domain, we need to prepare Active Directory.
To do this use the following procedure whilst working on the Small Business Server

NOTE: X: refers to the drive letter that has been assigned to your DVD Drive.

After the above command you will be prompted to confirm you wish to proceed by typing the letter C and pressing Enter

Step 4 – Make Windows 2008 R2 Server a Domain Controller of the Existing Small Business Server 2003 Domain

To make the Windows 2008 Server a Domain Controller is fairly straight forward, we simply click Start > Run  and type DCPROMO click OK.

This will check that the Active Directory Services Binaries are installed and if they are not, it will install them.  It will then start the Active Directory Domain Services Installation Wizard.

On the first screen, there is no need to check the ‘Use Advanced mode Installation’ check box, just simply click next.  On the operating System Compatibility screen click next.

On the ‘Choose a Deployment Configuration’ screen, select the radio box for Existing Forest and Add a domain controller to an existing domain.  Then Click next.

On the ‘Network credentials’ screen, the name of the domain should have been detected automatically.  Check this is correct.  If you are logged in as a user that has domain admin privileges then you can use the My Current logged on credentials option.  If not, click the set button and add the username and password that has domain admin privileges as shown in the screen above.  Click Next.

The following screen will give you the results of a domain search and ask you which domain you want to add this domain controller to.  As you are upgrading Small Business Server there should only be one.  Click Next.
The next screen will give you an option to select the site for the new domain controller.  If you have more than one Active Directory Site ensure that you select the correct one if it hasn’t been done by default.  Click next.

On the ‘Additional Domain Controller Options’ screen, make sure that both the DNS Server and the Global Catalog options are both checked.  Click Next.  The error message regarding DNS Delegation can safely be ignored.  Click Yes on this dialog to continue.

If you have separate folders where you want to store your log files, SYSVOL share and the Active Directory database then these can be specified on the next screen.  To be honest I keep them all as defaults.  Once done, click Next.

On the following screen, you are asked to set a password for Directory Services Restore Mode Administrator (DSRM).  Please note this is NOT the Domain Administrator password.  This password is used to boot the Domain Controller into Directory Services Restore Mode which is used for recovering corrupt/deleted/failed Domain Controllers.  Make a note of this password and keep it somewhere safe (in a fire safe for example).

Click Next on the following 2 screens.  The wizard will then start the promotion of the server to a domain controller (I always check the box on this screen to reboot on completion – This way you can leave it and come back to it knowing that it will be ready to continue).

Once rebooted your new server will be a domain controller, DNS server and Global Catalog server in your Small Business Server Domain.

Step 5 – Transfer DHCP Service

By default the Small Business Server will be the DHCP Server (if it isn’t and you’re using something else for DHCP, then you will simply need to update the DNS configuration this device is giving out so that it points to the 2008 Server instead of the 2003 Server) we will need to transfer this to the new server.

We can start this process by installing the DHCP Service.

To install DHCP, open up Server Manager and under Roles, click Add Role. From the list, select DHCP Server and click Next then next on the Introduction to DHCP Server screen.

On the network Connection Bindings screen you should have your primary IP address listed.  As you will be installing Exchange on this server it’s not recommended to have a multi-homed server but if you do make sure the LAN card and IP is the only one selected.  Click next.

NOTE: A multi-homed server is a server that has multiple IP addresses assigned to multiple Network Interface Cards.  Normally these types of servers would be used as routers.  Whilst Exchange can be made to work in this environment, it’s not recommended.

On the Specify IPv4 DNS Server Settings check the following settings:

Click next accepting the default settings on the WINS screen.

On the Add or Edit DHCP Scopes screen, click Add.  This will present you with the Add Scope dialog box.

On this screen enter the following details:

(This should be the same as the DHCP Scope you have configured on the Small Business Server).

You will notice in the scope I am creating, I have started from 192.168.10.15 this is so that I have 15 addresses that I can assign to fixed addresses.  My Small Business Server and Windows 2003 server will have an address below 192.168.10.15 but I might also have printers, photocopiers, and wireless access points that also need fixed IP addresses.  I have also left 192.168.10.254 available to use for my router.

Once you have completed all the details, click OK and then Next.

Accept the default setting on the ‘Configure DHCPv6 Stateless Mode’ and the Specify IPv6 DNS Server Settings.

On the ‘Authorize DHCP Server’ screen, select to use the current credentials and click Next, then Install on the confirmation screen.

The DHCP Server service is now installed on the Windows 2008 server.

Before we can switch over, we need to make some changes to the Small Business Server DHCP settings.  Whilst we can just turn one off and turn the other on this will cause you to have to release and renew the settings on the client machines manually for them to pick up the new DHCP Service.  The alternative is to wait the 4 days before your client machines request an IP address renewal.

To make the required changes, do the following on the Small Business Server:

In the section titled ‘Lease duration for DHCP clients’ we are going to change it to 2 hours from the default of 8 days.  Click OK

Then under Address Leases, highlight all DHCP Leases, right click and select delete.  NOTE:  If you have any reserved addresses make sure they are not highlighted otherwise they will be deleted also.

This action will cause all DHCP clients to renew their addresses and gain an address that has a 2 hour lease.  Check the Address Leases and refresh until you are happy that all the clients now have an IP address. (You might want to leave this overnight just to make absolutely sure)

Once you are happy that all the clients have now got a 2 hour lease from the Windows 2008 server do the following:

This will start the DHCP Service on the 2008 server and deactivate the service on the Small Business Server (this will happen automatically because when Small Business Server detects another DHCP server on the network it shuts its own down).

You will now find that in approximately 1 to 2 hours time, all your clients will start picking up IP addresses from the Windows 2008 Server.

You can now disable the DHCP Server service on the Small Business Server.  DO NOT disable the DHCP Client service, as this plays a part in DNS registration.

Now that all the clients are using the new Windows 2008 Server for DHCP and DNS, we need to make sure that the Small Business Server is also using the Windows 2008 Server for DNS.  To do this modify the TCP/IP properties of the network card and change the Primary DNS servers IP address to that of the Windows 2008 Server.  Do not enter anything in the Secondary DNS server.

Once you have done this restart the NETLOGON service so that the DNS entries are added to the Windows 2008 DNS.

Step 6 – Install Exchange 2010

Because we performed all the diagnostic checks at the start, the installation of Exchange 2010 should be fairly straight forward.  Please note that even though the installation of any version of Exchange Server on a domain controller is supported by Microsoft, it is not a recommended configuration.  But since we are migrating from Small Business Server the chances are you still want to stick with a single server configuration.

The first step is to install the pre-requisites on Windows 2008 to allow the Exchange 2010 installation to complete.  This can be done very easily using the Windows PowerShell.

To do this, please use the following steps:

Once the PowerShell is opened run the following commands:

There is no notification this has completed you will just see a flashing cursor waiting for input.  This command will allow us to add server roles and features via the PowerShell command.

This command will install all the pre-requisites for the Mailbox, Hub Transport and Client Access roles on to the Windows 2008 Server.  This will replicate what you currently have on the Small Business Server.
Once the server has restarted after the above command, launch the Windows Powershell again and run the following command:

This will set the Net.Tcp Port Sharing Service to Automatic instead of Manual

Install the Microsoft Office Filter Pack (which you should have downloaded earlier from the top list of required software).

Once we have done this, we need to prepare Active Directory for the Exchange 2010 installation.

Unlike previous versions, Exchange 2010 will detect if the schema updates have been done and do them if not, I prefer to see this happen.

To prepare Active Directory for Exchange 2010 we need to do the following:

Start the Exchange installation from the DVD.  On the initial splash screen that opens, click Step 3: Choose Exchange Language Options, select the appropriate option then click Step 4: Install Microsoft Exchange.  The Exchange Installation Wizard will then start.

The first screen you see is the Introduction screen, click Next.  Read, agree to and accept the license agreement screen.

This screen allows us to choose the type of installation.  As it’s assumed the Exchange 2010 server is a direct replacement for Small Business Server and all roles will be installed on a single server, we simply select Typical Exchange Server Installation and Click next.

If we were separating our roles out on to different servers we would select Custom Exchange Server Installation and then click next.

This screen allows us to specify what URL will be used for accessing our Outlook Web App from outside of the network.  Whatever you put in here you will need to make sure you have a DNS A record for it in your EXTERNAL DNS server.  In the later steps you will also need to use this name in your SSL Certificate Request. (CSR)

Check the box ‘The Client Access role server will be internet-facing’ and then specify the URL you will use, do not addhttps:// or anything at the end i.e. /owa.  Click next.

This screen is asking us to specify the Exchange 2003 server that the installation will create a routing group connector for.  This is essential for mailflow between the servers.  Click Browse, the list should be generated automatically and you will be able to select the Small Business Server from the list.  Click OK and then next.

Choose on the next screen if you wish to participate in the Customer Improvement program and then click next.  At this point the readiness checks will be performed to ensure your infrastructure is ready for Exchange 2010.

The results of the readiness check should show a warning on the Organisation Prerequisites, this is normal and it’s because we didn’t run the setup /PrepareAD /OrganizationName: command earlier on.  This can safely be ignored as the setup will perform this task for us.

The other cautionary warning you will see on my screen capture is simply because I haven’t installed the Office Filter Pack so you will only see this if you didn’t follow the step earlier.  Once you click install, the wizard will Install Exchange Server 2010.  And we are looking for the screen below.  All green.

Now that Exchange is installed, using the Exchange Management Console, navigate to Server Configuration > Hub Transport.  Here there will be 2 Receive Connectors listed.

The one we will be dealing with is the one that starts with the word Default and is followed by the name of the Exchange 2010 server.  Right click on this Receive Connector and select properties.  Under the Permission Groups tab, check the box for Anonymous Users.  If this box is not checked then servers sending mail to you will not be able to connect.  Your e-mails with therefore be rejected.

One final task before we move on, is to reconfigure any firewall/router rules you may have for ports 25 and 443 to allow the Exchange 2010 server to now deal with SMTP traffic and Outlook Web App.

Step 7 – Installing Exchange 2010 SSL Certificate

Exchange 2010 installs with a self-signed certificate by default.  Whilst this will work, it will cause browser errors in the form of untrusted websites, Outlook errors for Autodiscover (which is used for free/busy information & Offline Address Book) and errors when using mobile devices and Outlook Anywhere.  Whilst for the most part there are ways around these problems, I won’t be covering them in this article because my recommendation, as any other Exchange specialist would recommend, would be to use a 3rd party certificate.

Unlike earlier versions of Exchange, we have a nice easy to use wizard in the Exchange Management Console for certificate generation.  This makes installing commercial certificates in Exchange 2010 much easier and less prone to error.

To start the New Exchange Certificate wizard do the following:

This will start the New Exchange Certificate Wizard

Enter a friendly name for the certificate. This can be whatever you like, but standard practice is to use the company name or something that can identify your company.  Click Next
DO NOT Select to create a wildcard certificate unless you plan on buying a certificate for your entire domain, which is not required for Exchange to function.  Click Next

On the following screen pull down the arrows for:

Make sure all the URLs are correct (examples can be found in my screen capture above) and then click Next.

Confirm the entries on the next page (it’s worth noting on this screen that the address shown in bold is what is known as a Common Name).  This could be important later as Outlook Anywhere requires the common name to be the same as the URL used in the RPC connection.  In most of my configurations I use the owa.gkvirtualdomain.co.uk as the common name.  To do this, highlight the URL and click the Set as Common Name option.  Click next when finished.

You then need to complete your organisation information as shown in the screen above.  Then click New on the next screen. And then finish.

You can then open the file you have specified to create the request with, copy and paste the entire contents into the 3rd party vendors website and follow their instructions for submitting it.

Once you receive the signed certificate, right click on the certificate request located as above and select Complete Pending Request.  Follow the instructions to import the certificate you have just received.

Step 8 – Migrate Exchange Data

Now we have Exchange installed, it’s time to migrate the data over.  We will start with the easy part as a bit of a break from the previous 6 steps.

To migrate the user mailboxes, open Exchange Management Console and navigate to Recipient Configuration > Mailbox. Highlight the mailboxes you want to move (the mailboxes that are on the Exchange 2003 server will appear as Legacy Mailboxes, as pictured above), right click on them and select New Local Move Request

When the New Local Move Request wizard opens, click the browse option to select the Windows 2008/Exchange 2010 server mail store and click OK, then click next.

On the following screen, select what you would like to do when the wizard encounters corrupt messages. You have two options: either to skip only the corrupt message or to skip the whole mailbox.  Click next and on the following screen click New.

Once the move requests have been verified, we should see the screen above.  All the mailboxes you selected should hopefully show a green tick.  Please note that during the move mailbox process, the user will not have access to their mailbox as it is moved “offline”.

The next stage is to migrate the Public Folders. To do this complete the following steps on the SBS 2003 Server:

Now that we have moved the data to the Exchange 2010 server it’s best to leave this for a day or so to a) make sure all the data is moved before we perform any other Exchange related tasks. b) allow all the outlook clients to update automatically with the new server settings.

Step 9 – Migrate SharePoint Services

If you are using companyweb for an intranet/document storage etc. then you will also need to migrate this.  If you are not using SharePoint then simply skip this step.

First thing you will need to do is to install the Windows SharePoint Services 3.0 which you downloaded as part of the pre-requisites.  This is the free version of SharePoint Services.  Only the version with Integrated Service Pack 2 will install on Windows 2008 R2.

Once you have downloaded Windows SharePoint Services 3.0, double click to start the installation on the Windows 2008 Server.  Read, agree to and accept the license agreement and click continue.  Select Basic installation.  This will install the standard single site installation.

Once the installation has finished, launch the SharePoint Products and Technologies Configuration Wizard.  Click next on the welcome screen and Yes to confirm you are OK with the services being restarted.
NOTE: While IIS restarts, the Outlook Web App will be temporarily unavailable.

On the final screen, check the box to ‘Run the SharePoint Products and Technologies Configuration Wizard now’ and click Close.

Click Next on the welcome screen and Yes to confirm you are OK with the services being restarted.  The wizard will run through again and complete the configuration.   Once finished click close.

Make sure you install the 32bit version on the Small Business Server and the 64bit version on the Windows 2008 server.

The next step we need to complete is to run a pre-scan on the current database to allow Windows SharePoint Service 3.0 to upgrade it when we move it to the Windows 2008 server.
Perform the following steps to achieve this:

Once you have done this still, working on the Small Business server perform the following tasks:

We now need to launch the SQL Server Management Studio Express, this can be done by:

Before we perform any additional steps, we are going to take a backup of the database used for companyweb.  Follow these steps to perform a backup:

On the backup screen, the only section you need to change is the destination.  Make sure the “backup to” is set to disk and then click Add.

If you receive the error message above, don’t panic, it’s easily solved by using the following procedure:

Close Regedit and try clicking the Add button again on the Backup Screen, specify a location for where you would like to save the backup and click OK.

We are now going to detach the database from the SBS 2003 server.  Still in SQL Server Management Studio Express, right-click on the STS_SBSSERVERNAME_1 select tasks and then Detach.

Locate the Database and Log file, which by default will be located in C:\ Program Files\Microsoft SQL Server\MSSQL$SharePoint\Data on the Small Business Server.  You need to copy the STS_SBSSERVERNAME_1.MDF  and STS_SBSSERVERNAME_1_LOG.LDF files to a folder on the destination server, don’t copy them in to the SQL Server data folder.

Working on the Windows 2008 server perform the following steps:

We now need to create the website in IIS.  To do this, do the following:

On the Add Web Site wizard, enter a site name of companyweb, specify a physical path and host name of companyweb as shown in the image above.  You can change these if you wish, but keeping the site name/host name the same will mean the URL your clients use will not change.

Launch DNS manager from Start > Administrative Tools > DNS.  Expand the forward lookup zone for your internal domain name and locate the CNAME record called companyweb.  This should currently be using the Small Business Server’s server name.  Double-click this record to edit it and change it to use the Windows 2008 server instead.

And then finally we need to setup SharePoint Service.  To do this perform the following steps:

On the screen that appears, complete the fields as listed below.  If nothing is specified, please leave the default settings.
In the IIS Web Site Section choose the following:

In the Security Configuration Section

In the Application Pool Section

In the Database Name and Authentication Section

In the Search Server Section

Click OK and your SharePoint Website will be created.  Once the wizard has finished, from an Internet Browser type inhttp://companyweb/ and the companyweb website on the Windows 2008 server will be displayed.

Step 10 – Migrate shared user data

Because this step is so generic and it could be different for every server, I am not going to go into specifics, only the more general steps that need to be accomplished.

The shares that are in use on the Small Business Server need to be recreated on the Windows 2008 server.  One way we can do this is backup the share definitions from the Small Business Server and restore them to the Windows 2008 server.  This involves working in the registry so please be careful and follow the instructions accurately.  The instructions on how to do this can be found here: http://support.microsoft.com/kb/125996

The next stage is to restore the actual data to the shares.  This is a lot easier if you ensure that the folder structure you have on the Small Business Server for shares is replicated on the Windows 2008 server.  You can simply use Windows Backup to backup and restore the data.  This will keep all permissions and ownership information intact.

You will then need to update any login scripts which will be located in \\LOCALHOST\SYSVOL on the Windows 2008 server to ensure that any mapped drives are updated.

You will also need to update any attributes that may be under the Profiles tab in Active Directory Users and Computers for the users themselves.

Step 11 – Uninstall Exchange 2003 from Small Business Server 2003

Hopefully you are arriving at this step a day or two after you have migrated all the mailboxes, if not then I would recommend you leave it for a day or two just to allow all client computers to automatically update the Exchange server setting in outlook.  If you uninstall Exchange 2003 from the Small Business Server and this hasn’t happened then the clients will have to be changed manually.

To perform this task we will need Small Business Server 2003 CD 2, which will be asked for during the uninstallation.  Before we can do this though, there are a few steps we need to perform otherwise we will not be able to uninstall it.

If you use Recipient Policies that are Manage Mailbox policies, then these will need to be removed.  Likewise, if you have Recipient Policies that are used for both e-mail address definition and mailbox management, the settings defined under Mailbox Manager Settings will need to be removed.  You DO NOT need to remove your e-mail address policies.

The Recipient Update Service is not used in Exchange 2010 and is therefore not required, so it can be removed.  To do this you will need to use ADSI Edit.  This can be done by using the following procedure:

Only delete the Recipient Update Service entries under the container; DO NOT delete the container itself or any other entries

The final step in preparation for uninstalling Exchange Server 2003 is to delete the routing group connectors that would have been created as part of the installation.  I have highlighted them in the image below.  Simply right click on each connector and select delete.

We are now ready to uninstall Exchange 2003.  To do this, navigate to Start > Control Panel > Add or Remove Programs.  From the list of installed applications, highlight Windows Small Business Server 2003 and click Change/Remove.

Click next on the Welcome screen, and next on the screen that follows.  Once the component screen opens pull down the drop down next to Exchange Server and select remove, as shown below. Then click next and next again.

Step 12 – Transfer all 5 FSMO roles to Windows 2008 Domain Controller

Caution needs to be taken when performing this next step. I would advise that ALL of the previous steps need to be completed before this is done as Small Business Server MUST hold all 5 FSMO roles.
Once you are ready, the roles can be transferred as follows.  Working on the Windows 2008 server do the following:

That is 3 of the 5 roles transferred.  To do the next one, which is the Domain Naming Master we need to do the following:

4 down with 1 to go.  To move the Schema Master role we need to do the following:

That’s all the FSMO roles transferred from the Small Business Server.  The next and final step is to demote the server from being a Domain Controller.

Step 13 – DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network

This is the final step of the migration process.  If you have made it this far, well done!  This is the easy bit!

The first thing we need to do is make sure the Small Business Server is not a Global Catalog Server.  Click on Start > Administrative Tools > Active Directory Sites and Services.  Locate the Small Business Server as shown in the screen shot below.

Right click on NTDS settings located under the Small Business Server and select properties.  Remove the check from the Global Catalog check box and click OK.  Close Active Directory Sites and Services snap-in.

The final step is to run DCPROMO.  To do this, do the following:

The server will then remove Active Directory Services from the Small Business Server and it will no longer be a Domain Controller.

Once this has finished, allow the server to restart, login and then shut it down.  You have now completed the migration.

If you are still with me, well done!  There are a few sections of additional reading below if you would like to know some more detail about some of the processes we have just completed.  There is an excellent article from EE Expert tigermatt around the purpose of the FSMO roles which you will find under the further reading section.

Further Reading

Move/Migrate Sharepoint Services: http://technet.microsoft.com/en-us/library/cc288664.aspx
Move last legacy Exchange Server: http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx
Demystifying the Active Directory FSMO Roles by tigermatt: http://www.experts-exchange.com/articles/Software/Server_Software/File_Servers/Active_Directory/Demystifying-the-Active-Directory-FSMO-Roles.html

• Add, remove, and enumerate packages and drivers.
• Enable or disable Windows features.
• Apply changes based on the offline servicing section of an unattend.xml answer file.
• Configure international settings.
• Upgrade a Windows image to a different edition.
• Prepare a Windows PE image.
• Take advantage of better logging.
• Service down-level operating systems like Windows Vista with SP1 and Windows Server 2008.
• Service all platforms (32-bit, 64-bit, and Itanium).
• Service a 32-bit image from a 64-bit host and service a 64-bit image from a 32-bit host.
• Make use of old Package Manager scripts.

Command-Line Options

The HP Sizer for Microsoft Hyper-V 2008 R2 is an automated, downloadable tool that provides quick and helpful sizing guidance for “best-fit” HP server and storage configurations running in a Hyper-V R2 environment. The tool is intended to assist with the planning of a Hyper-V R2 virtual server deployment project. It enables the user to quickly compare different solution configurations and produces a customizable server and storage solution complete with a detail Bill of Materials (BOM) that includes part numbers and prices.

The HP Sizer for Microsoft Hyper-V 2008 R2 allows users to create new solutions, open already existing solutions, or use other types of performance data collecting tools, such as the Microsoft Assessment and Planning tool (MAP), to build rich Hyper-V R2 configurations based on HP server and storage technology. The tool allows rapid comparison of Hyper-V R2 characterizations using various HP server and storage choices.

Customers often ask “Given a hardware load-out X, how many Ys can I get/run/host?”

The frustrating answer always starts with “…it depends…”. We caveat this way not because we want to frustrate, but because it is true. Many teams will go on to say “We have tested the following in our labs and gotten the displayed results…”

1 X = thingy

2 X = more thingies

3X = many more thingies

While accurate, not super-helpful.

The truth is that to do good perf planning for Hyper-V you have to run some tests.

Run them using your actual production load (converted to Virtual Machines) in a test environment.

TIP: you can download the free VHD version of SCVMM, then run it as a VM to convert your production machines to “test” virtual machines.

Then play with your assumptions and tweak things higher and lower and to your design tolerance and actually observe how perf goes.

Add an overhead/forgot-to-test percentage, done.

So, how to do that for Hyper-V? Here are some perf testing resources to help you:

• Performance and capacity requirements for Hyper-V
• Hyper-V Performance FAQ
• Measuring Performance on Hyper-V
• Checklist: Measuring Performance on Hyper-V
• Performance Tuning Guidelines for Windows Server 2008
• Performance Testing Guide for Windows Paper
• Optimizing Hyper-V performance: Advanced fine-tuning
• Hyper-V Support, Performance and Load Tools
• Hyper-V How To: Set Up a Virtualization Test Lab using Windows Server 2008 Cluster, Hyper-V and simulated iSCSI…
• Hyper-V Server Sizing: How Much Memory for the Host?
• VM Perftuning: Minimize VM background processing
• Hyper-V How To: Balance VM I/O
• Monitoring Hyper-V Performance
• How to get Processor Utilization for Hyper-V via WMI
• Hyper-V Performance Counters – Part one of many – The overview
• Hyper-V Performance Counters – Part two of many – “Hyper-V Hypervisor” counter set
• Hyper-V Performance Counters – Part three of many – “Hyper-V Hypervisor Logical Processors” counter set
• Hyper-V Performance Counters – Part four of many – “Hyper-V Hypervisor Virtual Processor” and “Hyper-V Hypervisor Root Virtual Processor” counter set
• Hyper-V Performance Counters – Part five of many – “Hyper-VM VM Vid Numa Node

To identify and troubleshoot these issues, you can find more information from the KB articles:

• 975787 Adjust User Account Control settings in Windows 7
• 976832 Error message when you insert a smart card in a reader on a Windows 7-based or Windows Server 2008 R2-based computer: “Device driver software was not successfully installed”
• 975784 Enable the Quick Launch bar in Windows 7
• 975785 Customize the notification area in Windows 7
• 975786 Customize the notification area in Windows 7
• 975788 Turn off the secure desktop in Windows 7
• 976034 Get a detailed Power Efficiency Diagnostics Report for your computer in Windows 7
• 976170 Troubleshoot Aero problems in Windows 7
• 976877 Troubleshoot Aero problems in Windows 7
• 976736 How to install Windows PowerShell on a computer that is running Windows Server 2008 R2 Core
• 2006291 Error message When You Bring up the Server Manager Console and click on Add / View Roles: “0x800B0100″
• 977510 Authentication fails when an external client tries to log on by using a read-only domain controller in a perimeter network

Source: http://blogs.technet.com/ferris/default.aspx

vSphere Client on Windows 7 now supported

In case you didn’t notice, Update 1 for VMware vCenter Server 4.0 was released last week. This is great news for all of you who wish to run the vSphere client on Windows 7 machines.

While we had a KB article (Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2 (1011329)) which went through a couple of different incarnations as new information became available, we can now put this problem behind us. No work-arounds are necessary, it just works now.

Here’s a quote from the release notes:

Windows 7 and Windows 2008 R2 support — This release adds support for 32-bit and 64-bit versions of Windows 7 as well as 64-bit Windows 2008 R2 as guest operating system platforms. In addition, the vSphere Client is now supported and can be installed on a Windows 7 platform.

We highly recommend reading the entire set of release notes, they contain valuable information.

source : http://blogs.vmware.com/kb/2009/11/vsphere-client-on-windows-7-now-supported.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+VmwareKnowledgebaseBlog+%28VMware+Knowledgebase+Blog%29

A couple of things to note about this guide:

• I do not use Vista — I have never really used Vista and now with Windows 7 out there really is no reason to; however the steps here will work just fine with Vista installation sources
• I have only tested this using a USB stick and will only cover that method here – it’s much more flexible (and faster) for installation than using DVD — but DVDs should work just fine: you can find plenty of tutorials on the web that will tell you how to use oscdimg.exe to take the files we create here and turn them into a burnable ISO

WHAT YOU WILL NEED:

• USB stick, at least 4 GB (perhaps larger depending on how many OSes you plan to integrate, I use a 16 GB) that has been properly formatted using Steps 1 and 2 here
• ISOs or DVDs of the operating systems that you plan to integrate
• imagex.exe (can be found for download on the web, or you can download the full 1.7 GB WAIK here)
• computer running Vista or newer operating system (XP should work but I have not tested it)

STEP 1: Extract the operating system files

Take your various ISO files or DVDs and copy their contents into subfolders on your hard drive – in my case I have Windows 7 x86, Windows 7 x64, Windows 2008 R2, and Windows 2008 SP2 x86, so I created folders called e:\7×86, e:\7×64, e:\2008r2, and e:\2008×86    (E is the letter of my hard drive, not the USB drive).

STEP 2: Browse the WIM files and extract the desired editions

Open a WAIK command prompt, or browse to whatever folder you downloaded imagex.exe to within an administrative level command prompt.  Start by running the following command:

imagex.exe /info e:\7×86\sources\install.wim

This will display a big verbose mess that, once you parse through it, lists out all the editions embedded in the WIM file (and their associated index #).  Most default Microsoft WIMs will have multiple editions – in this case the ones in the Windows 7 x86 WIM boil down to:

• 1 Starter
• 2 Home Basic
• 3 Home Premium
• 4 Professional
• 5 Ultimate

Since Starter edition is basically worthless, I only want editions 2-5 in my custom WIM file, so I run these commands one after another:

imagex.exe /export e:\7×86\sources\install.wim 2 e:\install.wim “Windows 7 HOMEBASIC (x86)” /compress maximum

imagex.exe /export e:\7×86\sources\install.wim 3 e:\install.wim “Windows 7 HOMEPREMIUM (x86)” /compress maximum

imagex.exe /export e:\7×86\sources\install.wim 4 e:\install.wim “Windows 7 PROFESSIONAL (x86)” /compress maximum

imagex.exe /export e:\7×86\sources\install.wim 5 e:\install.wim “Windows 7 ULTIMATE (x86)” /compress maximum

I now have an install.wim file in the root of my E drive that contains only the editions I specified in these commands.  Next,  I want to integrate Windows 7 x64 so I repeat the above steps using the 7×64 path instead of 7×86.  You will notice that the x64 version of Windows 7 has no Starter edition, so the index numbers are not the same as the x86 source!  Also, since just about any machine new enough to run x64 is likely new enough to handle Aero graphics, I don’t bother with integrating the Home Basic version of x64 into my WIM – so I only add Home Premium, Professional, and Ultimate.

I then repeat these steps again using the Windows 2008 R2 source (here again I discriminate – I only pull Standard, Enterprise, Standard Core, and Enterprise Core because I have no use for the DataCenter or Web versions).  Finally, I integrate Windows 2008 SP2 x86 — I do this because I have a few older machines that are not x64 capable and therefore cannot run 2008 R2 (which is x64 only) – so for these machines I run Windows 2008 SP2 x86.

You can of course integrate any OSes and editions you like!  When you are done, you will have an install.wim file of varying size – mine is roughly 5.5 GB.  (not a big deal for the USB method, but for those of you planning on burning to DVD, you may have issues with WIM files that are larger than 4 GB…  To get around this see this link)

STEP 3: Finalize the USB stick

You must now choose which OS you want to use as the boot environment – this needs to be an x86 operating system if you plan to install any x86 OSes (because x86 OSes cannot be installed from x64 boot environments).  You also want to use the newest operating system you can, because you may encounter issues if you try to deploy an OS that is older than the boot environment - in my case I use Windows 7 x86 to ensure I can deploy any operating system I like:

• take the custom install.wim file (from E:\) and replace the install.wim file in e:\7×86\sources
• copy all contents from e:\7×86 to your USB stick

Now boot from the USB stick and you should see all your OSes, like below!

Source : This link.