>>We have just installed a new server with the following:
>>
>>processor: Intel(R) Xeaon(R) cpu 2.27Ghz and 2.27 Ghz (2 processors)
>>memory: 8:00 GB
>>os: Windows Server 2008 R2 Standard 64 bit
>>
>>moving from a Windows Server 2003 R2 (2.50Ghz, 3.25 GB ram)
>>
>>at this point majority of workstations are windows XP
>>
>>
>>
>>As we have migrated our application and users over to this new server the performance is slowing down quite noticibly from the old server
>>
>>Any suggestions on what we can look for and expect would be greatly appreciated.
>
>You could do some basic performance checking:
>
>- CPU and RAM usage in Task Manager
>- Storage/disk subsystem in PerfMon - Average Disk Queue Length is a good first measure, high numbers are bad, anything averaging over 3 is an indication your storage is not fast enough
>
>Check antivirus settings; maybe for test purposes disable real-time file scanning on the server and workstations. Or at least exclude VFP files/file types (including temp folder(s))
>
>Check that DNS is configured properly on the new server/network. If the new server is the PDC, all the workstations on its domain should use its DNS server as their DNS server. For example, if the new server's static IP address is 192.168.16.2, the primary DNS server on each domain member workstation should be set to that IP address. If instead the workstations have their DNS server(s) set to your ISP's DNS servers that can cause major slowdowns and general network weirdness. Of course, DNS on the server will need to be set up to forward to your ISP's DNS servers for requests that are not available locally.


Thanks for the suggestions. After hours of trying to track down what could possibly be wrong, IT was tracking down cables thinking there might be an issue and sure enough there was!!!!!!!!!

(blushing) discovered the new server was plugged into a 100mp swich rather than the 1Gig switch!!!! What a difference that makes!