S
sappel23
Hello everyone,
I recently had to fix some pretty bad setup in a network of a friend of mine: The external IT support had virtualized a Win2012 foundation server and put it on a VMWare ESXi system and added another Windows 2012 Standard as DC. This and additionally more than 15 users led to some serious license issues that needed fixing. This setup was running roaming-profiles with the old 2012 foundation server acting as a fileserver for shares and for the profiles itself. So to fix this, I needed to replace the fileserver functionality and I disabled roaming profiles, because we had some performance issues with those anyhow.
OK, so here is what I did:
This basically worked for almost 20 users. I have one user left with some issues, but not that important. What really gets me is the admin account itself: It still keeps looking for the appdata path on the old server and I can't find out why. I double checked AD user configuration, I enabled a GPO prohibiting the logon of roaming profiles and I check several path settings in the registry (HKCU/Software/Microsoft/Windows/CurrentVersion/Explorer/Shell Folders). But that doesn't prevent the Admin account to look for the appdata path on the old server.
Any ideas where to look next?
Thanks in advance,
Helge
Continue reading...
I recently had to fix some pretty bad setup in a network of a friend of mine: The external IT support had virtualized a Win2012 foundation server and put it on a VMWare ESXi system and added another Windows 2012 Standard as DC. This and additionally more than 15 users led to some serious license issues that needed fixing. This setup was running roaming-profiles with the old 2012 foundation server acting as a fileserver for shares and for the profiles itself. So to fix this, I needed to replace the fileserver functionality and I disabled roaming profiles, because we had some performance issues with those anyhow.
OK, so here is what I did:
- Installed a server 2019 standard as new fileserver, leaving the 2012 standard as the one and only DC in the setup.
- moved all the files from the 2012 foundation to the new server
- disabled roaming profiles (in the AD user configuration and gpo folder redirection settings)
- removed all roaming user profiles at the workstations locally
- new logon at the workstations with local user profiles (+ restoring the previously backed up user files)
This basically worked for almost 20 users. I have one user left with some issues, but not that important. What really gets me is the admin account itself: It still keeps looking for the appdata path on the old server and I can't find out why. I double checked AD user configuration, I enabled a GPO prohibiting the logon of roaming profiles and I check several path settings in the registry (HKCU/Software/Microsoft/Windows/CurrentVersion/Explorer/Shell Folders). But that doesn't prevent the Admin account to look for the appdata path on the old server.
Any ideas where to look next?
Thanks in advance,
Helge
Continue reading...