E
EvilPeppard
Now, I have for sure found a solution to the roaming profile and 60
second logoff time problem. I have to thank members at www.asitis.org
for helping find this solution
(http://www.asitis.org/archives/000134.html).
I am running both SP3 and SP4 Windows 2000 servers in my Citrix Farm.
The problem lies with VNC Server. I am running the infamous Microsoft
HotFix Q329170 on the SP3 servers. I found, on both the SP3 servers
with the HotFix and the SP4 servers, if I removed VNC Server my
roaming profiles started working again, the Userenv error disappeared
and my logoff time dropped substantially.
Now, there were a few hoops I had to jump through to get VNC to
uninstall properly before the roaming profiles started working. Please
read this whole post before starting.
When I did a regular uninstall, I would get a message stating some
components of VNC Server could not be removed and I needed to remove
them manually. I also noticed the VNC Server Service was still
registered and listed in the services. So this is what I did:
1. Go to the RealVNC or VNC program group (depending on your version)
and run the "unregister the VNC server service".
2. Open Control Panel and uninstall VNC. (May get message stating some
items could not be removed, remove them manually).
3. Reboot server
4. Once the server came back up, if you are running Citrix or Terminal
Server, immediately disallow remote logins.
5. Change user mode of the server to "install mode" by opening a
command prompt and typing "change user/install". (TS and Citrix only).
6. Run a fresh install of VNC and make sure you set the VNC Server
service to re-register. You may get prompted about the directory and
such already existing...overwrite everything and finish the install.
Once the install is complete, you may be asked to reboot. Reboot
server, disallow logins, change to "install mode" again and
immediately go to the Control Panel and uninstall VNC. This time it
will successfully unregister the VNC Server Service itself and
uninstall VNC completely.
7. Reboot the server.
Now your roaming profiles should be working again. Run some test to
see if they are. I would go to the folder of a test user where their
roaming profile would be stored and delete all the sub folders and
files, log in to a TS or Citrix server with that test account, then
log off, switch back to watch the folder where their roaming profile
would be stored and see if the files and folders reappeared.
NOTE: I have eight Citrix Servers in a farm. I did have trouble with
the above steps on 2 of the servers and still could not get the
roaming profiles to work and still had the 60 second log off time. I
had to run REGEDIT on these two servers, after following the above
steps, and delete every instance of VNC in the registry. (Obviously
use EXTREME CARE when messing with your registry. Updating your ERD
and backing up your registry first would be a good idea). Once I
finished searching the registry, I rebooted the servers again with the
cleaned registry and my raoming profiles started working on these 2
other servers as well.
Good luck to all those users and Administrators that have been
fighting this problem.
second logoff time problem. I have to thank members at www.asitis.org
for helping find this solution
(http://www.asitis.org/archives/000134.html).
I am running both SP3 and SP4 Windows 2000 servers in my Citrix Farm.
The problem lies with VNC Server. I am running the infamous Microsoft
HotFix Q329170 on the SP3 servers. I found, on both the SP3 servers
with the HotFix and the SP4 servers, if I removed VNC Server my
roaming profiles started working again, the Userenv error disappeared
and my logoff time dropped substantially.
Now, there were a few hoops I had to jump through to get VNC to
uninstall properly before the roaming profiles started working. Please
read this whole post before starting.
When I did a regular uninstall, I would get a message stating some
components of VNC Server could not be removed and I needed to remove
them manually. I also noticed the VNC Server Service was still
registered and listed in the services. So this is what I did:
1. Go to the RealVNC or VNC program group (depending on your version)
and run the "unregister the VNC server service".
2. Open Control Panel and uninstall VNC. (May get message stating some
items could not be removed, remove them manually).
3. Reboot server
4. Once the server came back up, if you are running Citrix or Terminal
Server, immediately disallow remote logins.
5. Change user mode of the server to "install mode" by opening a
command prompt and typing "change user/install". (TS and Citrix only).
6. Run a fresh install of VNC and make sure you set the VNC Server
service to re-register. You may get prompted about the directory and
such already existing...overwrite everything and finish the install.
Once the install is complete, you may be asked to reboot. Reboot
server, disallow logins, change to "install mode" again and
immediately go to the Control Panel and uninstall VNC. This time it
will successfully unregister the VNC Server Service itself and
uninstall VNC completely.
7. Reboot the server.
Now your roaming profiles should be working again. Run some test to
see if they are. I would go to the folder of a test user where their
roaming profile would be stored and delete all the sub folders and
files, log in to a TS or Citrix server with that test account, then
log off, switch back to watch the folder where their roaming profile
would be stored and see if the files and folders reappeared.
NOTE: I have eight Citrix Servers in a farm. I did have trouble with
the above steps on 2 of the servers and still could not get the
roaming profiles to work and still had the 60 second log off time. I
had to run REGEDIT on these two servers, after following the above
steps, and delete every instance of VNC in the registry. (Obviously
use EXTREME CARE when messing with your registry. Updating your ERD
and backing up your registry first would be a good idea). Once I
finished searching the registry, I rebooted the servers again with the
cleaned registry and my raoming profiles started working on these 2
other servers as well.
Good luck to all those users and Administrators that have been
fighting this problem.