Results 1 to 12 of Our current roaming profile system works but there are snags, one being the first time some one logs on it does not load a profile they get no settings, no start menu etc etc - it looks like a clean slate then they logoff and logon and then they get the roaming profile. This happens 1st time for anyone without a profile on the server.
Another issue is every now and then a certain group of PCs will decide to take 10 minutes to logon, strange thing with this is when 1 PC in a room starts the whole model range of those PCs do the same thing - and at random times. If we built the room from CD we will not have an issue at all, yet if we rebuild them using FOG they work for a while but there seems to be a chance that it occurs again some months later.
I think its some kind of network driver issue? It does not occur every where, like we have a model of 60 machines in two rooms which have started to randomly logon slowly yet our ICT suites up here with 30 machines each are unaffected.
The worst thing is these machines some times then begin to slow down upon logoff and shutdown? That setting must match in the GPO settings and the user account am I correct in that? For the first problem I am thinking that it requires a pre-built profile yet the googling I see says Win7 does not require one. United States English. Ask a question. Quick access. Search related threads.
Remove From My Forums. Answered by:. Archived Forums. Windows Server General. Sign in to vote. My server is new Dell T63 with Windows server Can someone help? You configure the Connection speed option and the Time option in the Group Policy setting. You log on to the client computer from a remote site by using a network connection.
The network connection has a fast link speed to the profile server and has high network latency. Note The high network latency causes the download speed on the computer to be slow.
In this scenario, the time that is required for you to log on to the computer is longer than expected. Note This issue also occurs when you do not enable the Slow network connection timeout for user profiles Group Policy setting. When you do not enable the Group Policy setting, the computer uses the default settings for the Connection speed option and for the Time option.
This issue occurs because the computer ignores the Time option and therefore does not consider network latency. When the client computer detects that the link speed is fast, the computer assumes that the network connection is fast. Then, the client computer starts to download the roaming profile, and you experience a slow logon process. This hotfix is also available at Microsoft Update Catalog. Important This hotfix has been re-released to address an issue in which the digital signature on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory This hotfix also fixes a regression issue in the Profsvc.
For more information about update , click the following article number to view the article in the Microsoft Knowledge Base:. You can use the Time option to adjust network latency. A supported hotfix is available from Microsoft. Gotta be the profile. Have you looked in the registry?
Compare for the current user between the two logins. How would one go about comparing the two profiles in the registry? There are thousands if not hundreds of thousands of keys and entries for each user. Each time user A logs in and maps a network drive, they're establishing a new connection and querying to traverse X folders, and view its contents. If this is slow every time, I would start by comparing the two user accounts in Active Directory:.
Do user A and B have the same logon scripts? If not, compare the two logon scripts to see what's different. Do user A and B have the same "Member of" membership to security groups? If not, find another person who does, and see if this problem exists for that user as well.
If user A and B have the same permissions, group membership, group policy objects applied, then let's look at the roaming profiles. THe benefit to this would be that if their network shares are NOT slow when using a temporary local profile, then the issue is definitely within the roaming profile folder or preferences itself.
If the problem does persist even with a temporary logon profile, then it's still having to do with permissions in some way. I am not sure what happened, but it seems to have fixed itself, so I am at a loss to even try to diagnose it now. So I thought this issue had resolved itself, but apparently it did not.
0コメント