O.k here goes, apologies as this is long winded.
We have a fully updated/service packed Server 2008 setup with AD structure. We have approximately 600 users and 300 machines on a mix of laptops/desktops built by SCCM on Vista 32 bit OS's and the problem is as follows. Randomly if a user logs on to a Laptop via wireless their profile will not load up they get a temp one, if they switch machines to another laptop the problem occurs again. To fix this requires any number of the following remedies:
Delete local machine profile
Delete local machine profile registry key (occasionally the keys have .bak at the end of them)
Reset Profile on the server
Once we do this they can use wireless laptops again, unless they come up against one they have used before and had a temporary profile issue. This recreates the issue meaning we have to go through the same cleaup process's again and is becoming a real pain. Usually once a user had this happen once they are more likely to have it again but we also get new people with the problem at a rate of 1 or 2 a week and as the laptop pool is accessed by any number of people there is no way to pin someone down to a specific machine.
I am really starting to beat my head against the wall now and the only thing I can even begin to think of as the cause is the Wireless as it only starts on laptops using wireless before spreading. Is it possible that the wireless is dropping out early on login/logout and causing the profile to corrupt as it hasn't finished communicating with the server?
Thanks in advance for any insights.
James Gant
We have a fully updated/service packed Server 2008 setup with AD structure. We have approximately 600 users and 300 machines on a mix of laptops/desktops built by SCCM on Vista 32 bit OS's and the problem is as follows. Randomly if a user logs on to a Laptop via wireless their profile will not load up they get a temp one, if they switch machines to another laptop the problem occurs again. To fix this requires any number of the following remedies:
Delete local machine profile
Delete local machine profile registry key (occasionally the keys have .bak at the end of them)
Reset Profile on the server
Once we do this they can use wireless laptops again, unless they come up against one they have used before and had a temporary profile issue. This recreates the issue meaning we have to go through the same cleaup process's again and is becoming a real pain. Usually once a user had this happen once they are more likely to have it again but we also get new people with the problem at a rate of 1 or 2 a week and as the laptop pool is accessed by any number of people there is no way to pin someone down to a specific machine.
I am really starting to beat my head against the wall now and the only thing I can even begin to think of as the cause is the Wireless as it only starts on laptops using wireless before spreading. Is it possible that the wireless is dropping out early on login/logout and causing the profile to corrupt as it hasn't finished communicating with the server?
Thanks in advance for any insights.
James Gant
