|
There are a few instances where constructing a pointer to the users profile (using @userid) falls down ...
1) The instance where a userid already exists on the workstation (say, a local account with the same name) - Windows will create a profile with USERID.DOMAIN to avoid the conflict.
2) If you rename a userid in the domain - the physicial profile on the workstation will not be renamed (thats because Windows maps the SID to the profile - not the name).
3) If you delete a userid in the domain, then recreate it with the same name - since the SID is different, Windows will create a new profile for the user like USERID.000 (assuming that the old profile still existed on the machine and was not cleaned-up before-hand).
Thats my take anyways, anyone else ?
-Shawn
| 
