File Server Resource Manager was first introduced in Windows Server 2003 R2, for configuring volume and folder quotas.
In order to install File Server Resource Manager, go to Control Panel – Add/Remove Windows Components – Management and Monitoring Tools – File Server Resource Manager
File Server Resource Manager Windows 2003 R2
IIS 6 has a default limit for the outbound TCP connections. It limits the number of outbound sockets that can be created. This limit is controlled with MaxUserPort in the registry.
Browse to this registry path on the target machine:
HKEY_LOCAL_MACHINE \ SOFTWARE\ Microsoft\ Windows NT \ CurrentVersion \ ProfileList
Now you have to identify the SID corresponding to the account you want to change the profile path. Continue reading
When you setup the Certification Authority on a Windows server, a certificate for the CA is created, which will be expired after 5 years (default). You can extend the CA’s life beyond the end date of its original certificate. You can renew the CA with the following command:
certutil -renewCert ReuseKeys (renews the CA with the existing key pair)
or
certutil -renewCert (renews the CA with a new key pair)
Follow these steps in order to uninstall and reinstall the Common Management Agent
“C:\Program Files\Network Associates\Common Framework\FrmInst.exe” /forceuninstall
[HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\Shared Components\Framework]
Nou you can reinstall the Framework Service with the following command:
FramePkg.exe /Install=agent /ForceInstall
Note: Get the latest FramePkg.exe from your EPO server.
When you upgrade from a Windows Server 2003 R2 Standard SP2 to Windows Server 2003 R2 Enterprise Edition SP2 you may have a problem with memory. In case you have more than 4GB RAM on the machine (my situation was with 8GB) you have to do the following:
Locate boot.ini (it should be on the root of C:\ drive)
Under [operating systems] find the entry of Windows (it will be something like multi(0)disk(0)……=”Windows Server 2003, Enterprise” /noexecute=optout / fastdetect
and add
“/PAE” at the end
So now you will have
multi(0)disk(0)…..=”Windows Server 2003, Enterprise” /noexecute=optout /fastdetect /PAE
Restart the machine and now you ‘ll see the correct memory size.
You are trying to connect on a Windows 2000 Standalone server and the terminal service ssessions are full.
terminal services sessions in windows 2000
On this example the Administrator is connected from console and also holds another session of TS.
Also user1 is connected through TS.
In order to disconnect one of these users enter the following command:
rwinsta /server:192.168.1.3 3 (IP address of the target server and ID number)
This command will disconnect user user1.
We know that when you install a driver in Windows it remains there until you uninstall it. You can follow this procedure in order to uninstall drivers for hardware that no longer exists on the machine:
By default when a pc / server connects to an SUS server, an susclientid is created on the pc / server. In case that you clone that pc / server, the same susclientid will exist on the cloned pc / server and the SUS server will only have one entry of this pc / server. In order to change it on the new pc / server you have to follow the following procedure:
1. Stop Automatic Updates service
2. run regedit and go to HLM/Software/Microsoft/Windows/CurrentVersion/WindowsUpdate
3. on the right site of Registry Editor delete SusClientId and SusclientidValidation
4. Start Automatic Updates service
5. open cmd and run: wuauclt /detectnow
Now a new susclientid will be created on the machine and in a few seconds it will be created on the SUS machine.
Tested on Windows XP SP3 for the moment.
How to transfer your server to a new machine (new hardware):
Scenario 1 : The hard and “clean” way
Install your operating system to the new machine. Prepare the environment to be exactly the same as the current server. Install latest service packs / updates / latest drivers and test your machine. Then comes the hard part that you have to stop the current server, in order to transfer (copy) the data to the new machine and prepare all the settings / permissions and anything else that has to be configured in order to work. Don’t delete anything from the old machine, so that you have a backup plan in case something goes wrong. If everything works ok, you have to test very well that everything works fine.
Scenario 2 : The easy way
Use Acronis True Image Universal Restore, Backup your server and restore it to any hardware that you want! I works fine! I have tested it with Windows 2000, Windows Server 2003 32bit, 64 bit and everything is working. The procedure is that you take an image of your machine, and then restore it anywhere you want. After the restoration you just have to install the drivers.