Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About theunknown

  1. Here's the code I use to force an auto domain logon. It's included in RunOnceEx.cmd at T-13. ::SETS AUTOLOGON KEY SET KEY=HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon ::ENABLES SINGLE LOGON REG ADD "%KEY%" /f /v DefaultDomainName /t REG_SZ /d DOMAIN REG ADD "%KEY%" /f /v AltDefaultDomainName /t REG_SZ /d DOMAIN REG ADD "%KEY%" /f /v CachePrimaryDomain /t REG_SZ /d DOMAIN REG ADD "%KEY%" /f /v DefaultUserName /t REG_SZ /d USERNAME REG ADD "%KEY%" /f /v AltDefaultUserName /t REG_SZ /d USERNAME REG ADD "%KEY%" /f /v DefaultPassword /t REG_SZ /d PASSWORD REG ADD "%KEY%" /f /v AutoL
  2. Sounds like ive been a little misunderstood. I didnt come here complaining, merely to explore what was causing the issue. On the off chance you missed it, ive also presented a solution that seems to have no side effects. Im here sharing it with someone else in my situation, how is it that people find that a problem? Since my posts no one has offered anything constructive... so why bother? On a more related matter, a slight explanation of those key's would be appreciated. Because from what i've found, its not necessary to use the command prompt at all. The code below should achieve the same thi
  3. Deleted, didnt realise this made it through
  4. My problem is, in a domain environment every time a new user logs in these three windows appear. That normally wouldnt worry me, but because of my GP's each of these windows present my users with "The command prompt has been disables, Please See your administrator" and requires a key press to continue. Im not sure how familiar you are with general user ignorance, but this would send them into a panic. If these keys could be run ONLY on the first login, that'd be fine. But in their current position (every new user) they're a problem for me. Regards, theunknown
  5. Im pretty certain your problem is a result of IE7, in the Application Installs thread i've presented a solution that ive found does wonders. Regards, theunknown
  6. Just ran into this issue myself, strangely deleting [what i believe are] the offending keys from the registry dosnt resolve the issue. Unfortunately in my situation (large network with cmd.exe disable) this would results in three black dialogs telling users they're doing something they shouldnt at every logon, looking forward to a permenant solution. On that note, I believe these keys are imported from NLITE.INF, i've removed the appropriate lines and am in the process of testing now... will udpate with results when i have them. As for your RunOnceEx issue, im betting you install IE7 somewher
  7. As im sure we're all aware by now, IE7 seems to break RunOnceEx. Given the large dependency i have on the feature (RIS, 350+ Machines With Many Different App Configs) i set about finding a solution so i could install IE7 at the T-13 stage and have my apps installed at first login. The solution's reasonably simple, grab a copy of IERNONCE.DLL from before IE7 (Latest I Have is 6.0.2900.2180) and replace the one found in the IE7 installer with that version. Setup completes successfully without breaking the usefull RunOnceEx keys. I'm aware nLite can integrate it (reportedly without breaking RunOn
  8. slight update for those interested, i ran into the need to exclude apps from certain rooms, this is the fix to allow it. change ::APPLYS APPROPRIATE KEYS FOR SITE/CURRENT ROOM/MACHINE for /f "tokens=1* delims=-" %%a in ("%COMPUTERNAME%") DO SET ROOMNAME=%%a if exist RoomConfig\ALLROOMS.txt for /f "tokens=* delims= " %%a in (RoomConfig\AllRooms.txt) DO if not '%%a'=='' call :%%a if exist RoomConfig\%ROOMNAME%.txt for /f "tokens=* delims= " %%a in (RoomConfig\%ROOMNAME%.txt) DO if not '%%a'=='' call :%%a if exist RoomConfig\%COMPUTERNAME%.txt for /f "tokens=* delims= " %%a in (RoomConfig\%COMPUT
  9. I found auto domain logons to be a problem when using only those four keys. Sometimes it would work and the rest persisted with a local logon. The following keys are the only way i managed to successfully auto logon to the domain everytime. ::SETS AUTOLOGON KEY SET KEY=HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon ::ENABLES SINGLE ADMIN LOGON REG ADD "%KEY%" /f /v DefaultDomainName /t REG_SZ /d DOMAIN REG ADD "%KEY%" /f /v AltDefaultDomainName /t REG_SZ /d DOMAIN REG ADD "%KEY%" /f /v CachePrimaryDomain /t REG_SZ /d DOMAIN REG ADD "%KEY%" /f /v DefaultUserName /t REG_SZ /d USERN
  10. check out the scripts posted Here particularly the one by myself, it describes a method to do network install's and a management system for various room configurations. Regards theunknown
  11. im not aware of a method to remove it completely, however in my RunOnceEx.cmd i use this line... REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\srservice" /f /v Start /t REG_DWORD /d 4 Essentially it disables the service so when XP starts for the first time post install, system restore is disabled. regards, theunknown
  12. Not sure how many people are interested in my RIS application install method, but figured i'd share it just in case. Basically my RunOnceEx.bat contains all the switches required for all available applications to install across my entire network (350+ machines). When it executes because of my site naming convention (EG C2-01) it breaks up the name to determin the room and required room config. From there it parses a pre set list for that room of what is needed and applies the appropriate keys to RunOnceEx. AutoLogon keys are added for a single logon then the machine is restarted. It logs on, i
  • Create New...