Search the Community

I'm having trouble getting staff users logged on to our schools new Windows 7 machines. Currently (on our winXP machines) users logon to a shared profile as managed through AD with the user profile paths all pointing to the same file. Write access to this profile is restricted. Our server is Windows Server 2008. Once a Windows 7 machine is added to the network and put on the domain any staff that logon are given a temporary profile that is deleted once logged off. I'm not sure where the issue lies, but this is not a simple "Go in and delete the profile" issue, because users do not have profiles there to delete. I have tried switching off temporary profiles through the default group policy, which just leaves users with a "Windows Profile Logon Service" error once their username/password is entered. Do I need to change something with our old shared profile to make it Windows 7 compliant? Are there other reasons why Windows 7 would not like our current setup? Once our users can logon I will then look into restricting access to the local machine, as our preferred way of working is to keep all the data on our server and backed up, users are given a home directory that is on a network drive. This is giving me a real headache since i'm replacing all our old WinXP machines with Win7 machines while trying to keep the setup the same. Thank you for any help.

Hey folks, I need to call upon the collective powers that be on this forum to try help figure out why Windows 10 logins randomly add ".domain" to a users profile within the C:\Users path Our major issue with this is that our group policy maps known folder locations to c:\users\username\Onedrive\ so when they login and get c:\users\username.domain\ as a profile path they dont get their desktop or documents redirected to the correct location. Onedrive which is setup to SSO on login also crashes out with a 0x8004de40 error We do not use roaming profiles or map home drives, everything in the profile section in AD is empty Now, I know the fix and workaround: 1) Log user off 2) Delete folder : c:\users\username.domain 3) Delete registry key machinename\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\sidnumber 4) Log user back in 5) Close OneDrive and open CMD to run netsh winsock reset catalog - This fixes the 0x8004de40 error However i would like to try get the the route of the problem and try implement a permanent fix so any assistance with this would be greatly appreciated, out of 200 daily logins by staff we have to tackle this issue on average 5 times per day, it's not the same staff and not the same computers the issue arises on so I am ruling out hardware and user account specific probable causes.

We are having a problem where our profiles set for staff/student are not loading properly, We have two issues where student are not getting there profiles loaded they dont get their documents and they do not get desktop icons and so are forced to log on and then log off again the second issue is staff are logging on and are NOT get the temp profile saying they couldn't get the full profile. The majority of the time they are recieving the start menu's, backgrounds and icons and mapped home folders. We use alot of group policy to share out settings but we have installed paper cut and a central print system and have found that the printers some times appear and some times dont - some staff can print and some do not have a printer when they try to select it. They seem to have loaded partial profiles but are not aware until they have been working for some time then are stuck to finish the jobs they are doing! Its getting alot of complaints and with 130 staff my ears are hurting! any one had similar of got any suggestions?

Users have been logging on to some Win 7 machines without a problem for ages but now, whenever ANY user logs on, it logs them on with a temporary profile... This is only happening on 5 machines in our PPA room. A new switch has been added in there (managed) recently. Could it be that? When I log on as a domain admin- it logs on without a problem... Nobody is using roaming profiles.