Demystifying the AutoExNT tool in the Windows Server 2003 Resource Kit

One of these tools, the AutoExNT Service, runs a batch file named autoexnt.bat without you having to log onto the system. To run a batch file automatically at startup (to map drives, install printers, copy files or start an application), you'd typically use the Windows Startup folder, logon scripts or Scheduled Tasks. These are all viable options that will handle most of your startup needs.

But what if your batch file or task needs to start in a certain order (because it is dependent on another process, service or application), and you want it to run before you have to log onto the system? This is where AutoExNT comes into play.

Installation of AutoExNT

1. Using a text editor such as Notepad, create a batch file named Autoexnt.bat. Include the commands you want to run at startup in this file, such as copy files or start an application.
2. Copy the Autoexnt.bat file you just created, the Autoexnt.exe, Servmess.dll and Instexnt.exe files (in the Resource Kit) into the %SystemRoot%\System32 folder on your computer.
3. To install the service, open a command console and type: instexnt install.

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Microsoft Windows Server 2003 Administration How to install Windows Server 2003 patches when offline Validating Windows server clusters with ClusPrep Exploring the Windows Server 2003 Resource Kit: Clusfileport.dll Exploring the Windows Server 2003 Resource Kit: Cmdhere.inf and CMGetCer.inf Windows server security management: Security expert roundup Windows server management with Remote Desktop Avoid DC restoration problems with authoritative restore Exploring the Windows Server 2003 Resource Kit: Confdisk.exe Exploring the Windows Server 2003 Resource Kit: Compress.exe and Expand.exe Exploring the Windows Server 2003 Resource Kit: Clusterrecovery.exe Microsoft Windows Server 2003 Administration Research Windows Server Monitoring and Administration Mark Minasi, Microsoft MinWin and you Perfmon made easy with PAL utility DirectAccess means 'always on' in Windows Server 2008 R2 Top five Server Core management tips for Windows 2008 Top free tools for Windows server administration Windows Server 2008 Learning Guide A quick guide to Server Manager for Windows Server 2008 Moving dynamic disks to a new Windows server A first look at Storage Explorer for Windows Server 2008 Tips for Windows domain controller optimization Windows Server Monitoring and Management How Windows Server 2008 R2 stands up to security checks BitLocker in R2 provides data protection for semi-protected servers Perfmon made easy with PAL utility Converting Citrix XenServer source machines to Hyper-V format Balancing Windows security with reasonable password policies Windows AppLocker in R2: Turning conventional security wisdom on its head Top 10 things you don't know about Windows Server 2008 R2 BranchCache makes branch offices feel like home When to use VM backups versus snapshots in Hyper-V Installing Server Core for Windows 2008 the easy way

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

Use of AutoExNT

• To test AutoExNT, open a command console and type the command net start autoexnt. You should see Autoexnt.bat file execute.
• Configure your service options by clicking Start-->Program Files-->Administrative Tools-->Computer Management-->Expand Services and Applications -->click Services. Double-click the AutoExNT service

• Select Automatic in the Startup type box.
• Use the Logon As property if your autoexnt.bat file requires specific privileges to run its commands.
• If necessary, set any dependencies that AutoExNT should wait for before starting. This is handy if your application or task requires another service, such as the Workstation service, to be running before it can execute.

There is one issue with AutoExNT: It does not normally work well with applications that have interactive consoles.

About the author: Tim Fenner (MCSE, MCSA: Messaging, Network+ and A+) is a senior systems administrator who oversees a Microsoft Windows, Exchange and Office environment. He is also an independent consultant who specializes in the design, implementation and management of Windows networks.

Rate this Tip To rate tips, you must be a member of SearchWindowsServer.com. Register now to start rating these tips. Log in if you are already a member. DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.