Sloth Posted January 31, 2013 Posted January 31, 2013 Hey Guys, I was on my 2003 box today and I noticed that there was a domain user's folder that was in C:\documents and settings\ the local security policy on the server only lets admins log in to the server so I was wondering if anyone knew how it was created. The users folder didn't have much in it just an applications data folder with only a few certificates in it, as well as ntuser.dat and a few other files. So it doesn't appear to be created from the default users profile... I thought some one may have ran a runas command but that creates a profile based on the default user. also under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList reg key the user shows up there but the "flags" dword is set to 5 where as other profiles that I have logged in with have other #'s the hkey for the user also lacks the ProfileLoadTimeLow and ProfileLoadTimeHigh dwords any help will greatly be appreciated.
featured_spectre Posted February 1, 2013 Posted February 1, 2013 Could have simply been copied by accident.
DMcCoy Posted February 1, 2013 Posted February 1, 2013 I have seen this on 2003 and 2008 servers, I never did track down the process that causes the profile creation, although I am sure it wasn't the users logging into the server.
Sloth Posted February 2, 2013 Author Posted February 2, 2013 (edited) Thanks for the replys guys :-) McCoy you are right. Because I figured out what was causing the profiles to be created. I pretty much looked at the contains of the profiles and thought that it may be something to IE since the certificates were in there and what not. Anyways I tried everything and no luck.. Since the contains of the profile had hashes and certificates in it I thought maybe I will try to encrypt a file on the users home folder... anyways I created a txt file encrypted it, checked my server and sure enough a profile was created.. it is pretty interesting looking back on it now. it makes since that the server would have to have some info about the user who encrypted the file on the server so that that user could then decrypt it and view it's contents.... So the culprit seems to be NTFS filesystem encryption. Edited February 2, 2013 by Sloth 1
Patrickv Posted February 18, 2013 Posted February 18, 2013 Remote Desktop Connection purhaps, I have seen an example of a domain user login into a server remotely.
MordyT Posted February 18, 2013 Posted February 18, 2013 EFS will do it since you have to spoof kerberous login or something like it. GPO to prevent EFS solved it for me.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now