![]() ![]() If there is a better solution present for older systems like mine (XP/2003), I'd like to know, it would certainly be valuable info. Today, it's merely a faded memory and you really can't find people that remember "the bad old days". Over the years, this "organic growth method" of installing more and more servers was curtailed as unit cost, power needs, virtualization, and budget-cutting took their toll. As a result of this mentality of the time, it wasn't uncommon for out-of-control server growth to occur in back rooms, and as a side-effect, the need for more licensing and seats to be purchased. A common occurance at the time was to simply purchase another machine, log it in, run the service, and stick the box in a corner. Because of this, it has taken a long time, nearly a decade, for Microsoft to come round and create adequate tools for supporting headless environments (witness PowerShell and 2008 without a GUI). The original question didn't specify what environment was being used, so I can only answer for the one I am familiar with.Īlso, the entire need-a-GUI thing is really an artifact of how Windows was sold and marketed, circa 1990's. Things have changed a bit since then, most people are running Win, both having newer features. ![]() Related to some comments below, this is being done from a perspective of a Windows XP or 2003 setup. Your other accounts have their own privs and are not related in this manner. Lock down that account to just the drive access for security. If you're stuck in a situation where it can't, you'll still need a desktop session to do this - so create a simple service account that is separate from the others, one that has the sole task of logging into a server and providing drive access. Set the machine to auto-logon when powered up, which in turn will run the script, from which the drives are mapped. you're talking about accounts that don't log into a desktop session.īut.if you do allow the account to log in as a desktop session.Ĭreate the account like you would any other user, and provide a logon script like you would any other user - but it's one that's specifically tailored to that account. Why not? My work does this all the time, although I suspect that your user accounts are probably a bit more restrictive than ours, i.e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |