Windows Computing

Run a Batch File Before Logging on to Computer

Windows 2000 or Windows XP can be configured to run a startup script that is a batch file, VB script or JScript by using Group Policies. As well we can use AutoExnt utility, from the Resource Kit.

The AutoExNT service permits an administrator to configure a Windows based computer to run a custom batch file when first starting the computer. Also, a user or administrator is not required to be logged on at the time this custom batch file runs.

To start using  AutoExNTdo the following steps:

Installing the AutoExNT Service

1. Using a text editor (such as Notepad), create a batch file named Autoexnt.bat and include the commands you want to run at startup in this file.
2. Copy the Autoexnt.bat file you just created, in addition to the Autoexnt.exe, Servmess.dll, and Instexnt.exe files located in the Resource Kit CD-ROM to the %SystemRoot%\System32 folder on your computer.
3. At a command prompt, type instexnt install, and then press ENTER.

You should then receive the following message:

CreateService AutoExNT SUCCESS with InterActive Flag turned OFF

To view the installation processes running on the desktop, you must install the AutoExNT service using the /interactive switch. For example, instead of typing instexnt install, you would type instexnt install /interactive at a command prompt, and then press ENTER.

Testing the AutoExNT Service
To test the AutoExNT service, log on to your computer with an account that has administrator credentials, type net start autoexnt at a command prompt, and then press ENTER. The Autoexnt.bat file should run in an MS-DOS window.

NOTE: The AutoExNT service includes a /interactive switch, analogous to the /interactive switch of the AT command. This switch permits you to view the status of processes as they run. Because no user environment variables have yet been declared when AutoExNT runs at system startup, you must use full path names.

Also, if you need a service to be running before you start running a dependent process, you may include a command to start this service at the beginning of your Autoexnt.bat file. For example, if your batch file has commands that require the Server service to be running, include a net start server command at the beginning of your Autoexnt.bat file.

Configuring the AutoExNT Service to Run at Startup
To configure the AutoExNT service to run at startup:

1. Click Start, point to Programs, point to Administrative Tools, and then click Computer Management.
2. Double-click the Services and Applications branch to expand it, and then click Services.
3. Double-click the AutoExNT service, click Automatic in the Startup type box, and then click OK.

How to Set Time Zone from Command Line

If you need to change Time Zone for a lot XP computers, you can do this by simple command:

RunDLL32.exe shell32.dll,Control_RunDLL timedate.cpl,,/Z Central Standard Time

to change Time Zone to Jerusalem (GMT+02:00) run the following command:

RunDLL32.exe shell32.dll,Control_RunDLL timedate.cpl,,/Z (GMT+02:00) Jerusalem

How to Repair .NET 2.x

If for what ever reason you need to repair installation of .NET 2. x, you can do this from command line by running the following command:
“C:\WINDOWS\microsoft.NET\Framework\v2.0.50727\Microsoft .NET Framework 2.0\install.exe” /qb! /norestart

Public blog “Windows 7”

The public blog “Windows 7” team has started - http://blogs.msdn.com/e7/archive/2008/08/14/welcome.aspx. It looks like the team will be blogging using this as one of the channels to talk to general public about the progress of Windows 7.

SBS 2008 Released to Manufacturing

Windows Small Business Server 2008 software has been finalized! 3 Days ago both SBS Standard and Premium are being released to manufacturing, so it will be widely available by November 12 launch. 

Windows NT Backup - Restore Utility on Vista or Windows 2008

I guess it’s impossible to find IT person who doesn’t know very old and at the same time very powerful program, NTBACKUP. For me, it a best program to backup and restore Windows systems, like NT, 2000, XP and 2003 :).

If you have an old backups that was made by NTBACKUP and you want to restore it on Windows Vista or Windows 2008 you can use recently released Windows NT Backup - Restore Utility.

If you have a reason ( I do) to use the old NTBACKUP program to do backup on Windows 2008 it’s also possible, but I’ll talk about how to do that in one of my next articles :).

Remote Desktop Connection 6.1 (RDP 6.1) on Windows XP WITHOUT SP3. RDP 6.1 on Win XP with SP2

Recently, on one Windows 2008 I’ve installed a Terminal Server Role and did a TS Web Apps. Really nice feature, you can get access to application through web interface, exactly how it’s done on Citrix, but by using Windows 2008 you not requested to buy a Citrix ;). Yes, TS Web Apps from Windows 2008 is a nice, but to get access to this application, on a client side should be installed RDP 6.1 client. This particular version of RDP cames with SP3 for Windows XP or with SP1 for Windows Vista. I have no idea why Microsoft doesn’t provide RDP 6.1 as separate package.
In my case I couldn’t install XP SP3 or Vista SP1 on every machine in Network, so I’ve found a workaround. The first step is to install a RDP 6.0. After that we need to get few files from XP SP3 or Vista SP1. Create anywhere on your disk directory, let’s say RDP6_1 and put there the following files:

lhmstsc.mui
lhmstscx.mui
mstsc.chm
mstsc.exe
mstsc.exe.mui
mstscax.dll

Inside RDP6_1 create directory en-us and put there the following files:

aaclient.dll.mui
mstsc.exe.mui
mstscax.dll.mui

NOTE: Remember to take all mentioned files from Windows XP SP3 or from Windows Vista SP1.

Now inside RDP6_1 create a batch update.bat. Here is a content of update.bat :

del c:\windows\$ntservicepackuninstall$\mstsc.exe
del c:\windows\$ntuninstallkb925876$\mstsc.exe
del c:\windows\servicepackfiles\i386\mstsc.exe
del c:\windows\system32\mstsc.exe
del c:\windows\system32\dllcache\mstsc.exe
del c:\windows\lastgood\system32\mstsc.exe

del c:\windows\$ntservicepackuninstall$\mstscax.dll
del c:\windows\$ntuninstallkb925876$\mstscax.dll
del c:\windows\servicepackfiles\i386\mstscax.dll
del c:\windows\system32\mstscax.dll
del c:\windows\system32\dllcache\mstscax.dll
del c:\windows\lastgood\system32\mstscax.dll

copy mstsc.exe c:\windows\$ntservicepackuninstall$\mstsc.exe
copy mstsc.exe c:\windows\$ntuninstallkb925876$\mstsc.exe
copy mstsc.exe c:\windows\servicepackfiles\i386\mstsc.exe
copy mstsc.exe c:\windows\system32\mstsc.exe
copy mstsc.exe c:\windows\system32\dllcache\mstsc.exe
copy mstsc.exe c:\windows\lastgood\system32\mstsc.exe

copy mstscax.dll c:\windows\$ntservicepackuninstall$\mstscax.dll
copy mstscax.dll c:\windows\$ntuninstallkb925876$\mstscax.dll
copy mstscax.dll c:\windows\servicepackfiles\i386\mstscax.dll
copy mstscax.dll c:\windows\system32\mstscax.dll
copy mstscax.dll c:\windows\system32\dllcache\mstscax.dll
copy mstscax.dll c:\windows\lastgood\system32\mstscax.dll

xcopy *.* c:\windows\system32 /e /y
regsvr32 %systemroot%\system32\mstscax.dll /s

Update.bat should be run after installation of RDP 6.0
Now, you can navigate to your TS Web Access and run RemoteApp Program.

What NAP is and how it works?

Yesterday was the first Windows 2008 event in Canada. The first event was in Toronto and had almost 3000 attendees. Twenty MVPs participated in Ask-The-Expert and I was one of them :). One of the commonly asked questions was question about “What NAP is and how it works?“

So, I’d like to show what posted on TheLazyAdmin.com about NAP:
With the recent launch of Windows Server 2008 you are no doubt spending all your free time playing around with everything new. One thing you might be playing around with is Network Access Protection. There is a great document on getting a DHCP based NAP lab set up but one thing the document is missing is how to configure the NAP client in XP SP3. In Windows Vista you simply start the service then enable the client through the NAP Client Configuration MMC (napclcfg.msc) but XP SP3 does not include the MMC. So how does one configure the NAP Client without a Nap Client configuration tool? Netsh, that is how!

To enable the NAP Client on XP SP3 you need to do the following:

1. Start –> Run –> Services.msc
2. Change the Network Access Protection Agent service to start automatically
3. Start the Network Access Protection Agent service
4. Start –> Run –> CMD.exe
5. Type netsh nap client set enforcement ID = ##### Admin = “Enable”
6. Start –> Run –> GPEdit.msc
7. Drill down to Computer Configuration | Administrative Templates | Windows Components | Security Center
8. Enable the Security Center
9. Start –> Run –> Services.msc
10. Start the Security Center service

You will need to replace the ##### with the ID based on whichever enforcement method you are using. You can use the following IDs for the various enforcement methods:

• DHCP = 79617
• RAS = 79618
• IPSec = 79619
• TS Gateway = 79621
• EAP = 79623

For more labs and information see:

Step-by-Step Guide: Demonstrate IPsec NAP Enforcement in a Test Lab

Step-by-Step Guide: Demonstrate 802.1X NAP Enforcement in a Test Lab

Step-by-Step Guide: Demonstrate VPN NAP Enforcement in a Test Lab

WAIK 1.1 for Windows Vista SP1 & Windows Server 2008

As many of you know, Microsoft released Windows Vista Service Pack 1 and Windows Server 2008 to Manufacturing RTM ! So, it’s a time to take a last Windows Automated Installation Kit (Windows AIK). The Windows Automated Installation Kit (Windows AIK) is designed to assist corporate IT professionals customize and deploy the Windows Vista and Windows Server 2008 families of operation systems. The Windows Automated Installation Kit (Windows AIK) is a set of tools and documentation that support the configuration and the deployment of Windows operating systems. By using Windows AIK, you can perform unattended Windows installations, capture Windows images with ImageX, create Windows PE images and much more.

Download WAIK1.1 here

Internet Explorer 7 (IE7) deployment - New white paper

Microsoft just released a new version of their IE7 deployment paper. The document has 156 pages. IE7 deployment can get tricky. Try to read this document before deployment, if you haven’t done it yet. It might be a useful reference if you run into problems.