• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2066
  • Last Modified:

Removing roaming profiles

Moving to virtual server environment. At the same time, going from Windows 2003 server to Windows 2008 R2. We are eliminating roaming profiles as our network is relatively small and there is no real need for them. Workstations mix of XP and Windows 7.

During the migration, we had original DC in place (Windows 2003). A new virtual server (Win 2008R2) was created and DCPROMO run. Additional servers added for Exchange 2010 and SQL2008. The 2 DCs were both running. Now nearing the end of migration process and looking to retire physical 2003 servers. ALL server roles transferred to 2008 DC, also DNS, DHCP, global catalog.

Windows 2003 server has shared folders for profile and tsprofile as roaming profiles were used in that environment. In ADUC all reference to profile and tsprofile path removed from user account properties. DCPROMO run on 2003 server to demote as a DC. Completed with no errors. 2003 server was powered off to test network access. Windows 7 workstations gave the following:

C:\windows\system32\config\systemprofile\desktop refers to a location that is unavailable. It could be on the hard drive on this computer or on a network. Check to make sure that the disk is properly inserted or that you are connected to the network and then try again. If it still cannot be located, the information might have been moved to a different location.

Could not receive a desktop. When the 2003 server was powered back on. Windows 7 stations logged on without issue.

How do I get the Windows 7 stations to logon once the 2003 server is powered off?
0
kingsville
Asked:
kingsville
  • 11
  • 9
  • 5
1 Solution
 
jrhelgesonCommented:
Interesting...
I'd go to the registry of one of these windows 7 comptuers and search for

"\system32\config\systemprofile" in the registry path...  I skip the c:\windows part because it could be referenced in a number of different ways (c:\windows, %systemRoot%, etc).

Also, run some Group Policy Modeling tests and see what GPO's are getting applied to those machines.

Joel
0
 
kingsvilleAuthor Commented:
Found only one instance in the registry in HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18

Name - ProfileImagePath
Type Reg_Expand_SZ
Data %systemroot%/system32/config/systemprofile
0
 
jrhelgesonCommented:
Have you verified that the path exists on that machine?
Do you have access to that profile path?
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
kingsvilleAuthor Commented:
Yes the path exists and I can access it.
If I open the desktop or Favorites subfolders they are empty - there is no information there regarding the workstation desktop or internet favorites  
0
 
jrhelgesonCommented:
But what it should have is the ntuser.dat file - a copy of the original clean registry created at system install.

Does this happen when users log in as themselves, does it happen when you log in as admin?  Is it specific to the user, or to the computer?

Joel
0
 
kingsvilleAuthor Commented:
yes there is an ntuser.dat in that folder.

I tried on 2 separate Windows 7 stations on SAturday when the old DC was demoted and received the same message on both
0
 
jrhelgesonCommented:
It is looking for the \desktop directory, does that desktop directory exist in that path? If not, could you try creating it?
%systemroot%\system32\config\systemprofile\desktop

Joel
0
 
kingsvilleAuthor Commented:
The desktop directory does exist already
0
 
johnb6767Commented:
rename the "C:\windows\system32\config\systemprofile\ntuser.dat" to "C:\windows\system32\config\systemprofile\ntuser.old and allow it to rebuild at the next bootup....."
0
 
johnb6767Commented:
Can also delete the Desktop folder there and allow it to recreate..... Or rename it to "Desktop-OLD".....
0
 
kingsvilleAuthor Commented:
I renamed ntuser.dat and a new one was created on restart. See this attached file please. note the circled path \\king2006\users......

This is the path to the old, retired domain controller. What is telling my station to go look for this path? This, along with the profile path \\king2006\profiles needs to be shut off. Is there a location in the Group policy to specify these path locations. In ADUC under user properties Profile tab and remote desktop services profile tab there are no longer any references to the former paths for roaming profiles.

Help!!!  
profile-message-edit.png.PDF
0
 
jrhelgesonCommented:
Okay, search the registry for King2006

I"m wondering if folder redirection was configured on the workstation, in addition to group policy.

I had a situation once where a Network Admin had redirected user profiles to a path on the server, but that it should only apply to new profiles on new computers (implemented on a go-forward basis).

Not realizing what he'd done (or not done, as it were)  He just thought it was flaky and then went to each computer that failed to redirect and manually set the folder redirection to the \\server\path for My Documents.

Once we moved the server to a new domain, all the automatically redirected ones worked.  Manually configured ones did not...  Seems kinda similar to your situation.

Have you verified that the user account in Active Directory does not have a home path set?

Joel
0
 
johnb6767Commented:
Statr>run>rsop.msc, and navigate to the Folder Redirection section, and see whats being applied to this user profile.
0
 
johnb6767Commented:
Or move this PC's account in AD to an OU with no policies applied.....
0
 
kingsvilleAuthor Commented:
Under the user properties in AD every user has a home directory which is now set to \\newserver\users$\%username% mapped to drive letter z:

This is working as expected for everyone. No one is having difficulty with obtaining or accessing the new home directories. We did not have Folder redirection setup in the old environment. Once this is resolved, I would lke to implement Folder redirection because we were starting to have difficulties with the size of some profiles.

Nothing is set at the station level. I am the only one that sets up new workstations and I do not set anything at the workstation level. All users had a profile path configured in AD to go to \\king2006\profiles\%username% - those paths were all deleted in AD and left blank

As for the last 2 suggestions (rsop and moving to another OU) - I will try this tomorrow morning when I get back in the office. If it is something in the default domain policy - it really will not matter where I move it correct?
0
 
jrhelgesonCommented:
You can put it into its own OU and have "Block Inheritance" on that OU.
0
 
johnb6767Commented:
Correct, but I hope that noone would have added that to the Default Domain Policy....
0
 
kingsvilleAuthor Commented:
I ran RSOP this morning. There was no reference to a "profile" folder location so I still do not have an answer as to why when this old server is powered down - Windows 7 machines cannot access a desktop. I am working this evening after hours to continue to troubleshoot.  

There IS a reference to tsprofile path in the Default Domain Policy under Computer Configuratin\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Profiles pointing to the old server location. Thin client users have accessed server path without issue and there are now profiles created and ready to go for the new environment. My problem is this server has to be retired once the migrations are completed this weekend. Can I create a similar tsprofile path in the new environment and simply copy over these profiles that were already created or I am going to need to start over
0
 
jrhelgesonCommented:
Have you searched the registry for old references to "king2006"?
0
 
kingsvilleAuthor Commented:
Yes - there are some registry references to king2006 for previous access to files, network shares. Nothing referencing a profile path of any type
0
 
jrhelgesonCommented:
Are any of the machines syncing offline files?

One thing you can do is set up a DNS CNAME that has redirects king2006 to the new server?
0
 
kingsvilleAuthor Commented:
offline files - none that I am aware of
0
 
kingsvilleAuthor Commented:
DNS has a host (A) record for king2006 as it is still online and running for the moment. Setup a CNAME for king2006 to poin to new server so that profie on next login will be saved there is all else is created equal?
0
 
kingsvilleAuthor Commented:
Ran RSOP on several stations and found settings in Default Domain Policy that we were unaware of going back to the original network setup. This allowed changes to be made in the Group Policy setup. Our Windows 7 machines now login when the old domain controller is powered off and messages regarding profile access have been corrected.
thank you
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 11
  • 9
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now