Microsoft
Software
Hardware
Network
Question : SBS 2008 has very slow file access and other problems after migration from sbs 2003
after migrating from a sbs 2003 to a sbs 2008 server, network access is very slow (it takes very long to to browse directories when you access them for the 1st time) and many workstation still want to connect "my documents" to the old (removed) sbs2003 server.
the new server has 16GB ram, 2x quad core xeon cpu's and runs on a dell r710 hardware. it serves about 40 users on 35 PCs and runs 2 sql-server instances. Load on cpu is minimal and about 60% of the ram is used.
I followed the microsoft guidelines for migration from the sbs2003 enviroment. problems started when we removed the 2003 server from the network.
dcdiag shows (except for some printer driver issues) no problems and sbs2008 bpa also has no red flags.
until now I have tried the following to speed up performance - but none helped:
- disabled the 4 onboard broadcom nic's and installed an intel gigabit nic
- enabled computer browser service
- upgraded forrest and domain to 2008
- removed all remains of the old sbs2003 server from dns
- did gpupdate /force on clients that still map wrong drives (also relogged 3 times there)
now I am fresh out of ideas where the problem could be - my guess would be somewhere in the AD/DNS (as I still have the problem with some clients that want to map "my documents" to the old server) but I can't seem to locate it.
Answer : SBS 2008 has very slow file access and other problems after migration from sbs 2003
HKEY_CURRENT_USER\Software
\Microsoft
\Windows\C
urrentVers
ion\Explor
er\User Shell Folders
HKEY_LOCAL_MACHINE\Softwar
e\Microsof
t\Windows\
CurrentVer
sion\Explo
rer\User Shell Folders
Random Solutions
Sql Sever 2005 scripts
Access VBA command to list Word docs for merging
Visual Basic Listbox to Textbox
HELP!!! I trying to repartition my C: sys drive on a Windows Server 2003
which is faster of the two...
C# Deserialize from a text file.
Ping a list of addresses in ms-dos
I am trying to compile an already produced program and it gets error 9009, which I was told has to do with the path of the batch program, where do I re-path the batch program correctly?
CIsco ASA
Batch file