Patrickv

I would warn you you must have 64 bit cpu to support windows server 2008. Here a few things you can look at 1) Check if the server connection speed. 2) Check if the server is on QoS port on your switch. 3) Check if you have any load balancing or restrictions on your connection on the server. That's all I can think of at the moment. I have a SBS 2003 not R2 and it works fine without raid.

Hmm, I am think it might be motherboard related. If you swapped it out with a new one and it still not working then it must be the connection point on the motherboard to SCSI card. I don't have experience with SCSI but that's what I would guess.

To answer your question. A mandatory profiles is a profile that doesn't save any changes when you logoff. When you login in next time you get a fresh copy of the mandatory profile. I find this useful in school setups.

hmm, looks like you got a bottleneck some where in your network. Their can be many factors. A router is mostly used for routing from network to another. I find a switch is best device when doing these operations unless you jumping from one sub-net network to another. Here are some things you can try 1) Check the physical LAN win 7 PC connection speed. 2) Check the wireless LAN win 7 PC wireless connection speed. 3) What kind of router you are using. 4) Have you tried having both win 7 on a physical connection than wireless. 5) Have you tried using a switch with this configuration A) Connect the internet router to the switch. (If needed) B) Connect wireless router to the switch. C) Connect win 7 PC to the switch. D) Connect NAS to the switch. 6) Check if their any load balancing on any device or computer 7) Check if their is any QoS. 8) Check your router configuration settings. 9) Swap ports with win 7 PC with the NAS. These are list of stuff I can come up a the time. If one of these h

I would like to let you know that windows 7 profiles can be a bit more bloated then XP. That's what i have found out. I had experience with a computer with local profiles is not a good idea. It take 10 more longer to setup a local profile than XP does. This pissed of a lot of users in that lab.

So you are you saying that your server lost it's physical drive letters? If so that can be easy fixed with Computer Management->Disk Management. It could be some registry screw up or virus.

It maybe that you have someone in your network trying to use that account by guess the password or using a dictionary brute force, or you have your lockout policy to high

I am thinking it's gota be a windows bug that no one has reported it.

hmm, I am assuming that you are storing the batch script you are trying to run in the netlogon folder and Server4 is your primary domain controller. if this is your script, then try and add "Pause" without quotes at the end of it. This just pauses the script and waits for user action. If nothing shows up then i can figure out further what your problem is. The netlogon share should allow you run batch scripts regards less if they are admin or not. net use n: \\server1\users\students\%username% /persistent:no net use o: \\server3\applications /persistent:no NET TIME \\server4 /SET /YES if exist \\server4\netlogon\screenres\%computername%.bat call \\server4\netlogon\screenres\%computername%.bat if not exist \\server4\netlogon\screenres\%computername%.bat call \\server4\netlogon\screenres\default.bat reg delete "HKCU\printers\connections" /f if exist \\server4\netlogon\printers\%computername%.reg regedit /s \\server4\netlogon\printers\%computername%.reg if not exist \\server4\netlogon\printers\%computername%.reg regedit /s \\server4\netlogon\printers\allprinters.reg

I find mandatory profiles tricky to configure. I find that keeping to profile size bellow 1mb would help improve speed. It depends on the server supplying the profile and the network. You can also do profile load sharing which you split one half of the users on 1 profile and the rest on the other.

Have you checked the stupid "User Account Control Settings". User Account Control Settings has some good things and some bad things when give system admins nightmares. This was the cause when I had a vb script to map my drives. Try turning it off to see if this helps.

I have seem to have the same problem with Windows 7 Professional on a HP Laptop. I have been also checking if the latest service or hot fix will fix this problem as i don't have the latest updates ATM. This problem occurs when you set a home drive using a windows 2003 server domain controller. Now because this a laptop that logs in with a domain account you can't always expect to be connected all the time to the network. As in the first post int the topic. No lag when connected to the network but soon as you are not connected a 20-30 sec login wait time. Why does Microsoft keep screwing up things when they a had it good because I did a test on Windows XP SP3 and it works fine. This only effects Windows 7. This happens when you have home drives on disconnect domain computers on Windows 7. Get rid of home drives and problem is fixed. I have made a quick fix with a batch script like: I am sure their is got to be a fix for this problem. Regards Patrick V