Roaming Profiles

[Guest Eric Lanyon]

My setup: Windows 2003 Domain Controllers, Windows 2003 Terminal Servers,

Windows 2003 File Server, Roaming Profiles, an abundance of GPOs and

ScriptLogic.

 

Scenario: My terminal servers (4 of them) would lock up and be unable to

write to the file server. Rebooting the file server would appear to clear

the issue, the terminal servers would freeze again....then after several

hours they would be fine. I then rebooted the file server into Safe Mode, no

more problems. But obviously can't run like this. I installed a clean

Windows 2003 File Server. I used MS Backup, backed up profiles, data and

restored to the new server. I modified GPOs, ran RSOP.MSC and corrected

anything I could see with the old fileserver name. Everything appeared fine.

Yesterday and today users are reporting extreme slowness logging into the

servers, Outlook hanging, taking forever to open Excel spreadsheets, etc. I

looked at my DCs and 1 of them on RSOP.exe pointed to a software install on

the old server name. I have disabled the original server's NIC so no

communication is occuring. Perhaps I should remove the shares and enable the

NIC? Any ideas???

[Guest Vera Noest [MVP]]

Re: Roaming Profiles

 

Your problem is hardly a TS-specific problem.

I'd post to a network or AD newsgroup.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?RXJpYyBMYW55b24=?=

<EricLanyon@discussions.microsoft.com> wrote on 04 mar 2008 in

microsoft.public.windows.terminal_services:

> My setup: Windows 2003 Domain Controllers, Windows 2003 Terminal

> Servers, Windows 2003 File Server, Roaming Profiles, an

> abundance of GPOs and ScriptLogic.

>

> Scenario: My terminal servers (4 of them) would lock up and be

> unable to write to the file server. Rebooting the file server

> would appear to clear the issue, the terminal servers would

> freeze again....then after several hours they would be fine. I

> then rebooted the file server into Safe Mode, no more problems.

> But obviously can't run like this. I installed a clean Windows

> 2003 File Server. I used MS Backup, backed up profiles, data

> and restored to the new server. I modified GPOs, ran RSOP.MSC

> and corrected anything I could see with the old fileserver name.

> Everything appeared fine.

> Yesterday and today users are reporting extreme slowness

> logging into the

> servers, Outlook hanging, taking forever to open Excel

> spreadsheets, etc. I looked at my DCs and 1 of them on RSOP.exe

> pointed to a software install on the old server name. I have

> disabled the original server's NIC so no communication is

> occuring. Perhaps I should remove the shares and enable the

> NIC? Any ideas???