You can brand your terminal server with your company’s logo so that employees will know they are connecting to the right place.
The image you select will appear behind the login screen. Simply create a BMP image file and add the path to the registry here:
HKEY_USERS\.Default\Control Panel\Desktop\Wallpaper
You have a folder with a large number of files that you need to delete. This is too much for Windows Explorer to handle.
FastCopy (it also deletes files fast)
It took several hours but FastCopy was able to delete 948,102 files without slowing down the server at all.
You try to connect to a server or shared folder and get this message:
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed…
You already have a connection to that resouce using a different username.
Disconnect your other connections then try again. Open a command prompt and type:
net use * /delete
When upgrading from Exchange 2003 to Exchange 2007, the setup wizard showed a failure because the Exchange 2003 server was still in Mixed Mode. I went through the normal steps to change it to Native Mode. However, the change was never seen by the Exchange 2007 setup wizard because the active directory attribute was never changed. Here’s how to change it manually. Keep in mind that this is probably a bad idea and you should fix whatever synchronization problem is preventing the attribute from changing normally.
To change the value of the msExchMixedMode attribute to False, follow these steps:
I recently decided to virtualize my dying Exchange 2003 server to give it new life on new hardware. I’ve had bad luck running the VMware Converter from within Windows (hot clone) on a domain controller in the past. I’ve also performed a hot cone with no issues at all so it is really a crapshoot as to whether it will work. I decided to play it safe this time and I did a cold clone by booting from the VMware Converter CD.
The conversion process went smoothly, although it took 12 hours to complete. Upon completion, it automatically booted up the new virtual machine. I woke up the next morning and went to log in and I was prompted for Windows activation. I tried to activate online and it failed. I called the number for telephone activation and they told me my product ID was invalid and I would have to call support. I called support and they said I would have to pay for emergency after hours service (this was a Sunday). So I was out of luck.
I happen to own a Volume License version of Windows Server 2003 – it just wasn’t installed on this server which came with the Dell OEM version. I decided to boot from the CD and run a Windows repair with my VL CD. After 40 minutes, the install was complete and Windows was booting…and booting. It spent 1 hour on Preparing Network Connections and I finally got a login prompt. I logged in and waited another hour for my desktop to appear before giving up. I turned my old server back on.
Moral of the story – make sure you are running a Volume License version of Windows BEFORE you convert it to a virtual machine.
After running promoting the new server to a domain controller (running dcpromo.exe)… On the new domain controller, follow these steps to migrate domain operations.
1) Open Active Directory Users and Computers
2) Right click on the domain, and go to “operations masters”
3) Each of the 3 tabs has a “change” button, click it to delagate the role to the new domain controller
4) Next, open Active Directory Domains and Trusts
5) Right click on “Active Directory Domains and Trusts” and go to “operations masters”
6) Repeat the change command from above
7) Wait several hours for the process to sync, and then you are free to remove the old domain controller from your network
Run dcdiag from the command line on your windows domain controller.
Run dcdiag /fix to fix common issues.
Always make sure your domain controller points to itself for DNS. This is a common mistake.
When browsing to a shared folder on my server, I go this error:
not enough server storage is available to process this command
This even happens on the server itself when browsing to \\servername\sharename
This happened after upgrading from Officescan 8 to Officescan 10 but it did not affect all servers that upgraded.
More info can be found here.
Set up a secondary zone for your domain on the new server.
Set it to point to your current DNS server as the master.
On the master server, allow zone transfers to the new server.
Wait for it to update.
Now, on the new server, change the Zone Type from Secondary to Primary.
On the current server, use netsh to dump your DHCP settings to a text file:
netsh -c dhcp server 192.168.5.9 scope 192.168.5.0 dump > c:\dhcpdump.txt
Note – the line above should use your actual server IP and scope.
On the new server, use netsh to execute a the dump file you just created:
netsh exec c:\dhcpdump.txt
Note – you should edit the dump file to include the IP of the new server before importing it.
