Hope this helped you resolve the error “The ordinal 410 could not be located”.

• Go to START – Run
• type “regedit”

Go to:

• HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\IEXPLORE.EXE\DefaultIcon

If your icon is missing the default icon properties will look like this:

1. C:\Program Files\Internet Explorer\iexplore.exe,-7.

What it should be is…

• C:\Program Files\Internet Explorer\iexplore.exe,-32528

Reboot. Your icon will now be back.

• Allow logon through Terminal Services
• Deny logon through Terminal Services

You can use these options to change the set of permissions a user must have to establish a Terminal Services session.
To establish a Terminal Services session, a user must have the following permissions:

• Allow logon through Terminal Services To grant a user these permissions, start the Group Policy snap-in, open the Local Security Policy or the appropriate Group Policy, and then navigate to the following location:

  Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment

• Allow logon to Terminal Server
  To grant a user these permissions, start either the Active Directory Users and Computers snap-in or the Local Users And Groups snap-in, open the user’s properties, click the Terminal Services Profile tab, and then click to select the Allow logon to Terminal Server check box.
• Guest Access: Logon to the RDP-TCP connection
  To grant guests Logon rights to the RDP-TCP connection, start the Terminal Services Configuration snap-in, edit the RDP-TCP so that the guest has at least Logon rights.

The pivotal difference between Windows 2000 and Windows Server 2003 is the "Allow logon through Terminal Services" user right. When you grant this user right, you no longer have to grant the user the Log on locally right (this was a requirement in Windows 2000). In Windows Server 2003, it is possible for a user to establish a Terminal Services session to a particular server, but not be able to log on to the console of that same server.

I got this information straight from the horse’s mouth.

1. You will have to burn the cd and boot from it.
2. Selected your language.
3. At the bottom right (or was it left) I clicked the Repair option.
4. Windows will do a quick scan then came back and say it found an issue with my startup files and asked if i wanted to repair and reboot.
5. I chose ok and reboot was successful!

I hope this helps you with the “Windows error 0Xc000000f windows failed to boot, Windows\System32\winload.exe is corrupt or missing” error.

The computer I was looking at today wasn’t so lucky. It turned out that it was much harder to fix. How I fixed it was:

1. Hit “Windows key” + “R”. This will open the run window
2. Type “regedit”
3. Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum
4. Right Click “Enum” and “change permissions”.
5. Make sure System has full control, everyone has read.
6. In my case this was already done. I went to the advanced section told it to replicate those permission to all sub-folders and files.
7. After doing so all my devices started showing up in device manager. Device manager was no long blank.

Hope this helps.

It’s important to only install printer drivers that are designed and built specifically for the Windows version you have.  This is particularly important for Windows XP; many of the CDs and floppy disks distributed with printers (particularly older models) do not have Windows XP drivers – check the printer manufacturer’s web site for printer drivers for the version of Windows you have (see Links).

A common cause of printer driver problems is to upgrade to Windows XP from Windows 95, 98 or ME without first removing the printer and the printer drivers.

The steps on this page will remove all printers and printer drivers from the computer.  The printing subsystem is then "clean" and ready for printers to be added using printer drivers specifically for the Windows version you have. 

If you have drivers for several printer models installed (e.g. on a Print Server computer) it may only be necessary to remove the defective printer drivers.  At steps 2, and 7, just delete the entries for the printers or printer drivers you suspect are defective.  Unfortunately, the files that comprise the drivers are all in the same folder.  Also, the same files may be used by the drivers for several printer models.  So, selectively deleting the driver files at step 12 may be difficult or impossible.  With Windows 2000 and XP, in most cases, deleting the registry entries for the drivers (step 7) will be sufficient, so you may want to skip steps 10 through 12 if you have multiple printer models and don’t want to re-install all of them.

Check in Control Panel, Add/Remove Programs; if there is an entry relating to one of the printers, select it, then click Change/Remove.  Follow the dialog and "uninstall all" or "remove all" as appropriate.  Some "printer software" have programs that show up here and it will be a good idea to remove those before going any further. 

If the Print Spooler service is operational:

1. Open the Printers (Printers and Faxes on Windows XP) folder

2. delete all of the printers

3. click File, Server Properties

4. select the Drivers tab

5. for each entry:

   1. select the entry

   2. click Remove

Usually, this will do a pretty good job of cleaning out drivers with Windows 2000 and later (not so with Windows NT 4). 

If the Print Spooler service is not operational, or you want to make certain there are no printer driver remnants, either follow the instructions below or use cleanspl.exe from the Windows 2000, XP or 2003 Resource Kit (http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en).  cleanspl.exe from the Windows 2003 Resource Kit tools will work on Windows XP. 

Some information about cleanspl.exe:

• cleanspl.exe does a very thorough job of cleaning up the print spooler stuff, but it does not remove the spooler service dependency on the Lexmark service (see special information about Lexmark printer drivers). 

• You can use it to clean up the spooler stuff on another computer (i.e. remotely). 

• When you run it, it asks you if you want to remove some things that are actually delivered (and installed by default) with Windows.  In most cases, you should answer No to the corresponding prompts (you don’t want to remove the Standard TCP/IP Port or the BJ Language Monitor).

Here’s how to clean up the print spooler stuff if cleanspl.exe is not available or you prefer to do things manually.

Warning! be very careful using regedit – if you delete the wrong things, you may render your computer inoperative!

1. open regedit (e.g. click Start, key regedit and press Enter)

2. navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers

under this key, there will be the keys Version-2 and Version-3 (one or the other of these may be absent – not a problem)

    the sub-keys under these contain the printer driver configuration information

delete all the sub-keys inside Version-2 and Version-3, but not these keys themselves

The Microsoft Knowledgebase article at http://support.microsoft.com/default.aspx?scid=kb;en-us;312052 lists some other registry entries to delete, but this is not usually necessary.

1. open a Command Prompt window

2. key the commands
   net stop spooler
          net start spooler

3. open Windows Explorer

4. navigate to %systemroot%\system32\spool\printers\ and delete any files there.  By default, this is where the print spooler stores print files.

5. navigate to %systemroot%\system32\spool\drivers\w32x86 (%systemroot% is usually Windows, but it might be winnt or something else; this is set when the OS is installed).

6. inside w32x86, there will be folders with the names 2 and 3 (one or more of these may be absent – not a problem)
          delete all of the files and sub-folders in each of the 2 and 3 folders, but not the folders themselves
        inside w32x86, there may be other folders with names starting with "hewlett_packard", "hphp" or something else; delete these folders also

7. restart the print spooler (see steps 8 and 9 above)

At this point, the system should be pretty well back to the way it was before any printers were installed.

Some would suggest restarting Windows at this point, but with Windows 2000 and later, this does not seem to be required.

If you have a Lexmark printer, these additional steps may be necessary (thanks to Robert Orleth [MSFT] for providing this information).  The Lexmark printer installation process sometimes installs a service that makes the print spooler service dependent on itself.  If there is a problem with Lexmark service or a Lexmark printer driver (or you removed it using the steps above), the print spooler service may not start (see also http://support.microsoft.com/default.aspx?scid=kb;en-us;324757).  The steps below make the print spooler service only dependent on the Remote Procedure Call (RPC) service (RPCSS), which is normal.  The print spooler service dependencies are stored in the registry at

     HKEY_LOCAL_MACINE\SYSTEM\CurrentControlSet\Services\Spooler\DependOnService

The sc config command at step 16 resets the value of that entry.

1. Open a Command Prompt window

2. key the command
          sc config spooler depend= RPCSS
   (note the space after the = but not before)

3. restart the print spooler (see steps 8 and 9 above)

1. Open up the Microsoft Exchange Console.
2. Find the user you are wanting to make the changes to.
3. Right Click the user and select properties.
4. go to the General tab and change the name.
5. Go to “User Information” tab and make sure each line is correct
6. Go to “Email Addresses” tab. Make sure both the SMTP and X400 lines are correct. Normally exchange leaves the old X400 address lying around. I always remove it.

Now that these changes have taken place you might think to yourself. I’m going to test this out! You open outlook and check to see if the Global Address list has been updated. You look and it hasn’t!

The reason for this is Exchange caches the Global Address via the Offline Address Book so that the system feels extremely quick. This caching however is not your friend when you want to see the changes right away. First thing you will need to do is:

1. Make sure you still have the Microsoft Exchange Console open. If it is not open please open it again.
2. There will be 3 types of configurations on the left hand side of the console. You want to click on Organization configuration
3. Under Organization configuration there will be Mailbox. Click on that.
4. Once you Click on Mailbox, in the main area of the Console you will see 5 tabs. The last one should be “Offline Address Book”. Click it.
5. Most people will only see “Default Offline Address Book”.
6. Right Click and select update.
7. This will force Exchange to get all that data you entered in the first few steps added to the Global Address Book cache.

You are now officially done with working with exchange. If people are still complaining about not seeing the right name you will need to get them to download the most up to date Offline Address book. Again since the client caches the Offline Address Book you will need to make sure the client has the most up to date version. (Note – I really don’t know how long a client will take to get the newer Global Address list. Some clients seem to get it within an hour while others seem to take up to a couple of days)

To update the Global Address list on the machines:

1. Open Outlook 2003/2007
2. Click on Options
3. Click Send/Receive
4. Click on Download Address Book…

Below are some of the screenshots from the steps above.

Make sure this is all filled in with the correct info.

This shows how to update the Offline Address Book.

Shows how to get Outlook Client to download the latest Offline Address Book.

As people begin to use Windows 7, Power Users and even regular users will eventually get around to wanting to expand their Windows 7 Libraries, which I think is an incredible feature, to include NAS locations.  Household NAS’s are now less than $200 for a terabyte, and home users and business users alike are going to be looking for this functionality.

Currently, Windows 7 does not support adding NAS locations to libraries.  I’m not sure why, but hopefully Microsoft deploys that functionality some time very soon.  Apparently, these locations break the Windows 7 backup functionality for that library.

Here’s the quick and dirty for the method I used.

The alternate method involves copying all the data from the NAS folder to a local folder.  One of the reasons for using a NAS to me, is to not have to have that information stored locally on my machine.  Anyway, here’s how I did it:

Method 1:

Create a temporary folder in a location of your choice, for example, I created a folder on my M: drive named “Linked Folders” and then created a sub-folder titled “ISO”.

M:\Linked Folders\ISO

Then add that folder to the library.

After adding that folder to the library, delete it. Then open a command prompt with administrator or elevated privileges, i.e. Run As Administrator. 

In case you don’t know, the command prompt program is located under the Start > All Programs > Accessories folder.  Right-Click the Command Prompt program and choose, Run As Administrator.

At the command prompt, type the following command:

mklink /d [path to folder that you deleted with the same name] [path to share location]

This makes my command look something like this:

mklink /d “M:\Linked Folders\ISO” \\nas02\public\ISO

You should get a message that states that the symbolic link was created.  You should now be able to see content under the library that you added through the link, and you should see a shortcut link in Windows Explorer in the location that you specified.

*** Remember that this will break the library backup, but you can backup the individual locations on your local drives. ***

Method 2

The alternate method is very simple, but keep in mind that ALL the data from the NAS folder will be copied to your local drive.

Right on the network folder or drive you want to include in the library and select “Always Available Offline”.  A sync will start.  You can then add that folder to a library.

Hope this helps someone out.  I really hope Microsoft just comes up with a fix instead of this workaround.

Check the network

Prior to working on the network, I suggest you download the Windows Server 2003 Support Tools to the old server from http://www.microsoft.com/downloads/details.aspx?FamilyId=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en. Once installed on the old server, you can run the command dcdiag from a command prompt, which tests the Domain Controller and verifies there are no present issues in Active Directory. This way, you can fix those issues before migrating. If all tests are passed, and only when all tests are passed, you should then run netdiag to test the network configuration of the server, and again ensure all tests pass before proceeding.

Install the new server

Firstly, install Windows Server 2003 to the new server. If you have the R2 edition, install Disk 2 of the CD-Rom media after initial setup completed and the system is up and running.
Once the new server is up and running, install drivers for the Network Card and any other necessary drivers. Then, once a Network Connection can be seen on the server and you can communicate over the network, configure the server with a static IP address on your network. At this stage, set the Preferred DNS Server to be the IP address of (one of) the existing Domain Controller(s). Do not enter any ISP DNS servers here.
Next, join the server to the existing Active Directory Domain. This is performed the standard way – in the same way as you join a workstation – through Start, Control Panel, System, Computer Name, Change. Choose the Domain option, enter the Domain Name and then press OK. A restart is required at this stage.

Prepare the Domain

If you will be installing Windows Server 2003 into a Windows Server 2000 domain, or Windows Server 2003 R2 into a non-R2 Server 2003 domain, you need to extend the schema. This involves placing the Windows Server 2003 media into the Domain Controller which currently holds the Schema Master FSMO role. For Windows Server 2003 R2, you must enter Disk 2, for other editions, enter Disk 1. For Windows Server 2003, browse, on the Schema Master, to the drive:\i386 folder at a command prompt. For R2 edition, browse on Disk 2 to the drive:\CMPNENTS\R2\ADPREP folder at a command prompt.
Once in the directory, the command dir should show the list of files available, one of which should be the adprep.exe tool. At the prompt, you should execute the command adprep /forestprep, to extend the forest schema. Once replication between all Domain Controllers in the Forest has completed – any only when that has occurred – you should then execute adprep /domainprep via the same procedure, and again, wait for replication to take place before proceeding.

Promote the server

After the reboot, you can now invoke the dcpromo wizard, used to promote the server as a Domain Controller. Start the wizard by entering dcpromo into the Start, Run box, then press OK. When prompted whether to enable Advanced Mode, I suggest unless you wish to see Advanced Features that you do not enable this feature. Follow through the wizard, opting for the ‘Additional Domain Controller in an existing domain’ when prompted. When the wizard completes, it will install Active Directory Services onto the server. Do NOT press ‘Cancel’ at this stage. If you made a mistake, wait for the wizard to complete, when you can restart the server and re-run the dcpromo wizard to correct the issue.

Install DNS

DNS is a crucial part of Active Directory, used for the whole of the Active Directory system. As a result, we must migrate DNS from the old DC to the new DC.
The easiest route to do this is to use Active Directory-integrated DNS, so that the DNS replicates from Domain Controller to Domain Controller with Active Directory replication traffic. To check whether your DNS zones are Active Directory-integrated, look on your existing Domain Controller in the DNS console (Start, Control Panel, Administrative Tools, DNS). Under Forward Lookup Zones, look for <yourdomainname.com> in the list. Beside the zone in the ‘Type’ column, you should see ‘Active Directory-integrated’ noted. If it does not report this, right-click the zone, choose Properties, then on the General tab beside Type, press the Change button and check the box marked ‘Store the zone in Active Directory’. Press OK.
Now the zone is stored in Active Directory, we simply need to install DNS on the new Domain Controller, and the DNS information will replicate in due course. To install DNS on the new server: Start, Control Panel, Add/Remove Programs, Add/Remove Windows Components. Click ‘Networking Services’, then press the Details button. Check the box to enable ‘Domain Name System (DNS)’ and then press OK. Pressing Next will install the new roles you have checked (DNS, in this case).
Once DNS is installed, it could take a short amount of time before the data shows up in the DNS console on the new server. However, it will show up in due course, so be patient; you don’t even need to manually create the zones.

Global Catalog

In a single-domain, single-forest environment, all Domain Controllers should be Global Catalog servers. The Global Catalog contains a partial replica of all objects in the forest, and is used to establish Universal Group Membership at logon. Without it, logins may not work properly, if at all. Thus, the new server should be a Global Catalog server.
To achieve this, on either the old or the new server, open the Active Directory Sites and Services tool from Administrative Tools in Control Panel. In the tool, expand the site which owns the server, then expand the server object itself. Within the server object, you will see an object entitled ‘NTDS Settings’. Right-click on this, press Properties and then check the box marked ‘Global Catalog’. OK out, and then it is necessary for replication to take place before the server will become a full Global Catalog.

FSMO Roles

The final step is to transfer the FSMO Operations Roles from the old server to the new server. The Operations Roles dictate the DC which performs particular Active Directory tasks. For example, the Schema Master role dicates upon which server the Schema can be extended.
To transfer these roles to the new server, follow the instructions in this Microsoft Knowledgebase article: http://support.microsoft.com/kb/324801. Note: Verify any information you read is based on the TRANSFER of the roles. SEIZING is not applicable here, and should not be performed for a graceful DC migration.

DNS Server on the new server

At this stage, DNS should have replicated, so you should now set the Preferred DNS Server on the New Server’s Network Card to point to the IP of the new server, and that IP address only. Do not enter any ISP DNS servers. It is recommended you use the full IP address of the server, rather than the loopback 127.0.0.1 address.
You may wish to enable Forwarders in the DNS console. Since no workstation or server should have the ISP’s DNS server manually configured on its NIC, the forwarder at the server enables DNS on the server to resolve the IP address of external domains using the ISP’s DNS server. See http://technet.microsoft.com/en-us/library/cc773370.aspx for details

Test

Finally, before demoting the old server, I would shut down or unplug the old server from the network, then test network resources and verify everything – particularly logins – works properly. You may find that the workstations are still detecting the DNS Server as the old server. This would need to be manually overridden to be the new server for test purposes.

Demote

If everything is working, then you can, at this stage, reconnect the old server, boot it up and then run dcpromo and choose the options to demote the server. Before disconnecting it from the network fully, you must remember that data and any other applications on the server must be transferred to the new server. ROBOCOPY is a good tool for doing this, since the /COPYALL switch enables you to copy the NTFS ACLs along with the actual data (Windows’ standard Copy operation will not carry the security permissions over).

Hope this helps

Graphical way of enabling Connectivity Logging in Exchange Server:

Open the Exchange Management Console

Find the server that has the “Edge Transport server role installed”. If you only have one exchange server install this should be pretty easy to find. Select the server in the “Hub Transport” section.

Once the server has been selected the Action Pane should change. Select Properties as seen below.

Find the “Log Settings” tab and check off “enable connectivity logging” and hit “OK” to save the changes. *NOTE* Make sure to note where the log folder is located.

How to enable Connectivity logging in Exchange Server via Powershell script

Script Format

Set-TransportServer <ServerName> -ConnectivityLogEnabled <$true | $false>

Real World Example

SetTranportServer Exchange07.domain.com - ConnectivityLogEnabled $true