Tuesday, July 31, 2007

MS: Loading Unsigned Drivers in Windows Vista

Atsiv is a command line tool that allows the user to load and unload signed or unsigned drivers on 32 and 64 bit versions of Windows XP, Windows 2003 and Windows Vista. Atsiv is designed to provide compatibility for legacy drivers and to allow the hobbyist community to run unsigned drivers without rebooting with special boot options or denial of service under Vista.


Thursday, July 26, 2007

MS: How To Obtain The Latest Update Rollup for Exchange 2007

This article describes how to obtain the latest update rollup for Microsoft Exchange Server 2007. Update rollups are a common way to distribute Exchange 2007 fixes (Hotfix) and Exchange 2007 modifications. You can install the latest update rollup to help keep the product up to date.


Monday, July 23, 2007

MS: How to Perform an Unattended Install of Windows XP

This document explain how to Perform an Unattended Install of Windows XP

  • How to perform an unattended install of Windows XP
  • Create a Basic Unattended CD Step by Step
  • Create an Advanced Unattended CD Step by Step
  • OEM Distribution Folders
  • Add drivers to unattended setup
  • The WINNT.SIF file for advanced unattended CD
  • Install applications using the unattended setup
  • Remove folders to save CD space
  • WINNT.SIF Extra Switches
Download the document in PDF format here

VMware: How to install Microsoft Windows 2008 Core on VMware Server

How to install Microsoft Windows 2008 Core (Beta 3) on VMware Server

This document explain how to install Windows 2008 Core (Beta 3) on VMware Server.

  • Create a Virtual Machine for Windows 2008 Core
  • Install VMware Tools
  • Set or change the administrative password
  • Change the screen resolution
  • Configure the network card (IP Address, DNS, WINS, Firewall)
  • Rename the server
  • Join the machine a domain / Workgroup
  • Remove the server from the domain
  • Restart the computer
  • Remote Desktop
  • Windows Update
  • System Properties
  • Configure Pagefile
  • Hotfix Management
  • Applications Management
  • Drivers Management
  • Activate the server
  • Services and Process Management
Download the document in PDF format here

Friday, July 20, 2007

VMware: Change the Screen Resolution on Windows 2008 Core (on VMware Server)

To change the screen resolution on a Windows 2008 Core you have two choices:

1) Run regedit.exe on another computer to remotely access the registry on the Server Core.

2) Change manually.

The registry key with the resolution information is:


Under this key will be a list of GUIDs and you will need to determine which one corresponds to your video card/driver. Under the GUID, you can set:


For example: To change the resolution on a VMware Server, search for "Device Description"="VMware SVGA II"

To manually change resolution on a Windows 2008 Core server on the Command Prompt type:

reg export HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video /s video.reg

Then you will need to edit the video.reg, change the resolution (The values are on Hex), remove the rest of info and save the file.

This an example from VMware Server machine at 800x600:

---- Start Video800.reg ----
Windows Registry Editor Version 5.00



---- End Video800.reg ----

Finally at the command prompt type:

REG IMPORT Video800.reg

MS: Insufficient System Resources Exist to Complete the API Error

The computer occasionally does not hibernate and you receive an "Insufficient System Resources Exist to Complete the API" error message in Windows XP with Service Pack 2, in Windows XP Tablet PC Edition 2005, or in Windows XP Media Center Edition 2005

When you experience this problem, the hibernate feature is not available on the computer until you restart the computer.

This problem typically occurs when the computer uses 1 gigabyte (GB) or more of RAM.


Thursday, July 19, 2007

MS: Windows 2003 SP2 SLP and Exchange Problems

Windows 2003 SP2 Scalable Networking pack and its possible effects on Exchange

MS: SMS 2003 Product Documentation

Systems Management Server 2003 Product Documentation

Systems Management Server 2003 Concepts, Planning, and Deployment Guide

Systems Management Server 2003 Operations Guide

MS: Unattended Install DOSHERE.INF

To unattended install the nice tool from PowerToys DOSHERE.INF you will need to create a new registry file and run using REGEDIT /S DOSHERE.REG

--- Start DOSHERE.REG file ---

[HKEY_CLASSES_ROOT\Drive\Shell\cmd]@="Command Prompt Here"
[HKEY_CLASSES_ROOT\Drive\Shell\cmd\command]@="cmd.exe /k \"cd %L\""
[HKEY_CLASSES_ROOT\Directory\Shell\cmd]@="Command Prompt Here"
[HKEY_CLASSES_ROOT\Directory\Shell\cmd\command]@="cmd.exe /k \"cd %L\""

--- End DOSHERE.REG file ---

MS: Third-Party Solutions for SMS

Web Sites:

MyITForum is the premier online destination for IT professionals responsible for managing their corporations’ Microsoft Windows systems; it is especially useful for IT professionals working with Microsoft Systems Management Server. (

FAQshop endeavors to provide a “one-stop-shop” for systems management questions, answers, and utilities. (

SMS Alliance is a consortium of companies that leverage joint resources to strengthen the capabilities and benefits of SMS. Their mission is to provide organizations with the best-of-breed solutions and services to enhance and extend SMS 2003. (

1E is one of the founding members of the SMS Alliance, 1E is a company on the cutting edge of systems management. It enhances and extends Microsoft management and deployment technologies, delivering advanced automation and reporting across the enterprise. (

Macrovision Corporation, another founding member of the SMS Alliance, Macrovision Corporation is a recognized leader in software deployment packaging, software installation, and software updating solutions. They offer one of the best software packaging tools with AdminStudio.

PS’SOFT, as a founding member of the SMS Alliance, offers extenders for SMS 2003 that focus on IT asset management. They offer a web-based software cataloging system called SMS Software Requests. (

Vintela, another founding member of the SMS Alliance, Vintela offers a seamless solution to extend security and compliance of Microsoft Active Directory to Unix, Linux, and other platforms and applications. They offer solutions that help IT administrators manage Unix, Linux, and MAC systems using SMS 2003. Vintela is now part of Quest Software. (

iAnywhere, the last founding member of the SMS Alliance, iAnywhere offers frontline security and management to SMS and provides extensions to manage your enterprise’s mobile and wireless devices through SMS. (

AppDeploy is the Internet resource to go to when you need to script or repackage an application for distribution. Among other points of interest at the site is a massive library of applications, sorted by application name and vendor name. For each application listed, you’ll find a community-based thread discussing the best practices, links, scripts, and challenges met/overcome with working with the application in regard to installation scripting/repackaging.(http://www.appdeploy.com/)

DesktopEngineer is perhaps one of the best resources in the Windows Installer arena. This site offers a wealth of information on Windows Installer technology, techniques, and troubleshooting tips. I have noticed that he is starting to increase the content related to Microsoft’s upcoming PowerShell scripting language. (http://www.desktopengineer.com/)


SMSView is a utility that is used to extend the functionality of the Microsoft Systems Management Server 2003 advanced client. SMSView allows you to perform the following actions on an SMS advanced client: All nonadmin users to view current mandatory assignments and advertisement status, View advertisement history (past 60 days), View current mandatory assignments, Rerun advertisements, Remote operations (remotely view and manage the SMS client), Display hardware/software inventory status, Display management point/proxy management point, Repair the SMS advanced client. (

SMS 2003 Monster MOF is a MOF file that contains several new classes of MOF that will improve SMShardware inventory capabilities. The Monster MOF will enhance inventory data without requiring intimate knowledge of the SMS_DEF.MOF file. (

SMS 2003 Web Remote Tools assist SMS administrators and allow client administration from a web page. (

Corey Becht’s Right-Click Tools is one of the best set of tools for all SMS administrators. This tool allows you to right click on any collection or individual PC within the SMS Administrator console and initiate hardware inventory, reassign the site code, restart the SMS Agent Host service, rerun advertisements without modifying the advertisement, perform discovery, initiate software inventory, create file collections, monitor software metering usage, refresh machine policies, evaluate policies, update Windows installer sources,change port number, and change cache size.These tools can run per computer resource or for all the members of a collection.(

Microsoft SMS Toolkit 2: Microsoft released a very nice set of tools for SMS called the SMS Toolkit version 2 . It contains the following tools: IIS Lockdown 2.1 Template, URLScan 2.5 Template, Policy Spy, SMS Trace, Advanced Client and Management Point Cleaner, Advanced Client Spy, Policy Verifier, Send Schedule, Management Point Spy, Set Preferred Distribution Point and CAP, Delete Certificate, Patch Management Evaluation, Delete Group Class, Transfer SMS ID, Package Loader, Management Point Troubleshooter, Client Site Assignment Verifier, Site Boundary Tool, Create Secondary Site Tool, Create SMS Address Tool.(

Security Logon Audit Tool (SLAT) extends SMS hardware inventory to include user logon information.This data can be used in web reports and queries. The tool includes the following samplereports: Top users for all systems, User logon information for a specific computer, Systems where the last logged-on user is not the top user, Systems where a specific user has logged on SLAT searches the security event log for the 528 event, which is created when user logon events occur and is enabled via Group Policy. (http://www.systemcentertools)

Enhanced System and User Discovery Tools, out of the box, SMS 2003 does a pretty good job of discovering systems from Active Directory. It’s not perfect, though—there are a few gaps in its methods. The Enhanced System Discovery tool, assists in filling these gaps. Out of the box, SMS 2003 does not perform Windows NT 4 domain discovery. This tool solves that by enumerating all machines from a list of NT 4 domains, resolving their IP addresses from DNS or WINS, and creating data discovery records for each system. (http://www.systemcentertools/)

BITS Bandwidth Manager is an SMS Installer script that lets you throttle BITS bandwidthon Windows XP SP2 systems. You do not need to manually adjust any settings. The script takes care of the Registry key manipulation for you.(http://www.myitforum.com/inc/upload/11332BITSManager.zip)

1E SMSWakeUp: this WOL product is able to turn on computers after they have been shut down by users. The wake cycle can be triggered on a regular schedule to power up systems in preparation for the workday, or to perform software deployment activities. (http://www.1e.com/)

1E NightWatchman: Since we are talking about waking systems that have been shut down, it maybe a good practice to examine how best to shut down those systems in the first place. Why dowe want to shut down systems? We do this to enforce reboot cycles and to save energy costs. (http://www.1e.com/)

1E SMSNomad Branch: Some offices may not have the server hardware to allow for a Distribution Point (DP). But those offices may have a substantial number of users and/or be separated from the rest of the network by a low-speed or saturated WAN link, which you would rather not send multiple copies of a package across. SMSNomad Branch acts similar to a peer-to-peer network, allowing other computers to become DPs. If one machine is shutdown, another is selected as the DP. Included in this technology is multicast, increasing its efficiency to reduce network traffic on the local network segment. (http://www.1e.com/)

1E OSD Plus Pack: This is an enhancement to the SMS OSD Feature Pack. It allows you to leverage the SMS OSD Feature Pack in offices that do not have DPs. OSD Plus Pack offers similar functionality to SMSNomad Branch, but also has a few other applications bundledwith it: State Migration Editor, which is an interface for the User State Migration Tool, AppMigrator, which allows the automatic reinstallation of applications after OS imaging, PXE Lite, which is a local PXE server to allow deployment of OS images to bare-metalmachines booted from the network PXE server. (http://www.1e.com/)

SMS Companion 2006: This product provides WOL capabilities, similar to 1E’s SMSWakeUp, but leverages slightly different technologies behind the scenes. A key difference is that SMS Companion puts systems in hibernation, rather than powering them off. The following are some of the key applications included with this product:Wake-on-Schedule: Allows clients to come out of a hibernation state. Service Windows: Allows you to restrict the SMS inventory and software distributions from happening during specific time periods, to reduce or eliminate user interruptions. Load Balancing: Allows you to reduce peak network and SMS server loading by making sure that the clients use these resources in a controlled manner. (http://www.smsexpert.com/)

Quest Management Xtensions for SMS: Since Windows platforms are not the only systems in an enterprise, you may need a way tomanage other platforms, such as Unix, Linux, and Mac OS X. These management extensions offer that capability for SMS 2003. One of the unique aspects of this product is its support route: first-level support is handled by Microsoft Product Support Services. (http://www.quest.com/quest-management-xtensions-for-sms)

MS: Redirect Desktop or Favorites to a Different Disk or Folder

Sometimes you need to keep your desktop or your favorites in a different disk partition or folder, in my case for backup purposes.

You will need to modify two registry keys:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

Saturday, July 14, 2007

VMware: Install Windows Vista x86 on ESX Server 3.0

1) Create a new VM with at least 512 MB of RAM and a 16 GB Hard Disk.
2) Copy the IMG/ISO of Windows Vista and the Floppy drive image to the ESX host using Veeam FastSCP, or insert the DVD and a Floppy with the driver into the ESX host.
3) Connect the IMG/ISO file to the Windows Vista VM. Make sure the "Connected" is selected.
4) Power on the Windows Vista VM.
5) Vista install starts and then stops at a point where it can't find the CD/DVD driver. A pop-up with "Load Driver" as the title appears indicating that a required device driver at this point.
6) Connect the Floppy drive image (and ensure "Connected" is selected).
7) After ESX has attached the floppy drive, click on "Rescan".
8) Continue the Setup of Windows Vista.
9) Remove the floppy image from the VM or uncheck "Connected".

Download the Floppy Image with the CD-ROM Driver from http://sti.epfl.ch/intranet/informatique/virtualisation/drivers-vista-rtm-esx.flp.zip

Thursday, July 12, 2007

VMware: Veeam FastSCP for ESX Transfer Timeout

Cannot transfer or edit files on ESX. Transfer timeout. No data transferred in the last 20 seconds.
To fix this problem please check whether the EMC AAM Client is opened for outgoing connections. It should be open to get FastSCP 2.0 work.
(You can enable it through the VI client: Configuration->Security Profile->Properties)

VMware: Exchange Server 2003 Performance on VMware ESX Server 3

This paper discusses the performance and scalability of Microsoft Exchange Server 2003 when deployed within virtual machines running under VMware ESX Server 3.01.


Wednesday, July 11, 2007

VMware: VMware Converter Runtime Error

When you run the VMware Converter v3.0.1 you get this error:

Create the C:\TEMP directory, and then correct Enviroment Variables for the current username and System Variables (Control Panel, System, Advanced,Enviroment Variables)

Tuesday, July 10, 2007

VMware: SSH Access to ESX Server 3.0

Direct root user ssh connections are disabled by default in fresh installations of VMware ESX 3.0 (VI3). Two options:

1) The recommended way to access the system is to ssh to the server as a non-root user and then use the su command to switch to the root account; this leaves an audit trail for accountability purposes.

2) An alternative way to allow root access is to configure ssh to allow the root user to log in.

Edit the ssh configuration file:

* vi /etc/ssh/sshd_config
* Find PermitRootLogin and change to yes (use ESC, then Insert)
* Save the changes (ESC then :wq!)
* Restart the ssh daemon: service sshd restart

3) You can download Veeam RootAccess Wizard from http://www.veeam.com
Veeam RootAccess Wizard helps you to enable or disable remote root access, or create a regular non-root user account. The newly created non-root user will belong to the default ‘users’ group and will be automatically granted remote ssh access. Su or sudo commands can then be used to elevate to the root account for privileged operations.

Thursday, July 05, 2007

Script: Detect VirusScan Installed in a Remote Machine

@echo off
rem * Change MachineName Here *
set machinename=

rem * Change UsernmeName Here *
set username=Administrator

rem * Change Password Here *
set Password=Passw0rd

net use \\%MachineName%\C$ %Password% /USER:%Username%
\\%machinename% query mcshield findstr /i "mcshield"
if not errorlevel 1 goto Installed

echo ** Virusscan NO installed **
goto VSEnd

echo ** Virusscan 8.0 installed **
Goto VSEnd


Remove HP Universal Print Monitor

To remove the HP Universal Print Monitor you'll want to go into the registry and delete the following entries:




You can delete this key using this command in a script:


Wednesday, July 04, 2007

MS: Exchange 2007 IMAP4 Client Access Configuration

1. Set MSExchangeIMAP4 service to automatic
Set-service msExchangeIMAP4 -startuptype automatic

2.Configure IP Address and Port for IMAP4

a.To set the IP address and port for communicating with Exchange using IMAP4 with SSL, run the following command:
Set-IMAPSettings -SSLBindings: IPaddress:Port

b.To set the IP address and port for communicating with Exchange using IMAP4 with no encryption or Transport Layer Security (TLS) encryption:
Set-IMAPSettings -UnencryptedOrTLSBindings IPaddress:Port

3.Configure IMAP4 Authentication - IMAP4 (143) /IMAP4 SSL (993)

a.If you will not be using TLS encryption and you want to allow Basic authentication on an unsecured port, run the following command:
Set-IMAPSettings -LoginType PlainTextLogin

b.If you will not be using TLS, but you want to restrict Basic authentication to use only secured ports, run the following command:
Set-IMAPSettings -LoginType PlainTextAuthentication

c.If you want to use TLS encryption before authentication, run the following command:
Set-IMAPSettings -LoginType SecureLogin

4.Enable IMAP4 Protocol for the User Mailbox (Enabled by default)
Set-CasMailbox MailboxName -IMAPenabled:$true ($false disables the protocol for the specified user)

5.Configure the SMTP Receive Connector on the Exchange Server to Allow Anonymous in order to send Email using the following command:
Set-ReceiveConnector "Servername\default Servername" -PermissionGroups “ExchangeServers,ExchangeUsers,ExchangeLegacyServers,AnonymousUsers"

6.Restart the Microsoft Exchange IMAP4
ServiceRestart-service MSExchangeIMAP4

7. Check the status of the Microsoft Exchange IMAP4
ServiceGet-Service MSExchangeIMAP4

8.Dump the IMAP4 configuration

Note: Remember do not use the Administrator account to test IMAP4, IMAP, SMTP.

MS: Exchange 2007 POP3 Client Access Configuration

1. Set MSExchangePOP3 service to automatic
Set-service msExchangePOP3 -startuptype automatic

2.Configure IP Address and Port for

a.To set the IP address and port for communicating with Exchange using
POP3 with SSL, run the following command:
Set-PopSettings -SSLBindings: IPaddress:Port

b.To set the IP address and port for communicating with Exchange using
POP3 with no encryption or Transport Layer Security (TLS) encryption:
Set-PopSettings -UnencryptedOrTLSBindings IPaddress:Port

POP3 Authentication - POP3 (110) /POP3 SSL (995)

a.If you will not be using TLS encryption and you want to allow Basic authentication on an unsecured port, run the following command:
Set-PopSettings -LoginType PlainTextLogin

b.If you will not be using TLS, but you want to restrict Basic authentication to use only secured ports, run the following command:
Set-PopSettings -LoginType PlainTextAuthentication

c.If you want to use TLS encryption before authentication, run the following command:
Set-PoPSettings -LoginType SecureLogin

POP3 Protocol for the User Mailbox (Enabled by default)
Set-CasMailbox MailboxName -Popenabled:$true ($false disables the protocol for the specified user)

5.Configure the SMTP Receive Connector on the Exchange Server to Allow Anonymous in order to send Email using the following command:
Set-ReceiveConnector "Servername\default Servername" -PermissionGroups “ExchangeServers,ExchangeUsers,ExchangeLegacyServers,AnonymousUsers"

6.Restart the Microsoft Exchange
POP3 Service
Restart-service MSExchangepop3

7. Check the status of the Microsoft Exchange POP3 Service
Get-Service MSExchangepop3

8.Dump the POP3 configuration


Note: Remember do not use the Administrator account to test POP3, IMAP, SMTP.

Tuesday, July 03, 2007

MS: Terminal Server Printer Redirection Wizard Tool

This tool will help resolve Terminal Server Printer Redirection errors by scanning the event log of a Terminal Server or Citrix server to create a custom mapping file for administrators.

The Terminal Server Printer Driver Redirection Wizard will help you troubleshoot and replace print drivers that were unsuccessfully redirected. This tool automates the process found in the Microsoft Knowledge Base article KB239088 entitled “Windows 2000 Terminal Services Server Logs Events 1111, 1105, and 1006”. http://support.microsoft.com/?id=239088

This tool will scan a server’s System Event Log and detect all events with Event ID 1111 and Source ‘TermServDevices.’ These events occur when a client machine has a printer driver that the Terminal Server does not recognize.

You can download the tool here

CTX: Event 39 - The CDM redirector has timed out a request to SessionID XX

Event Type: ErrorEvent
Source: CdmEvent
Category: NoneEvent
ID: 39
Date: 03/07/2007
Time: 5:07:34
User: N/A
Computer: SERVER
Description: The CDM redirector has timed out a request to SessionID XX.

This can happen when an application is attempting to access a client device during a disconnect. Check Citrix Server Administration when you see this event appear.
The best way to determine what client device is causing this issue is to turn off client device mapping (client drive, client COM ports, client printers).
Enable them one at a time and monitor the client's logon process.


Increase the settings for the following:

RequestTimeout: Default is 60 (seconds)
DirCacheTimeout: Default is 30 (seconds)
CacheTimeout: Default is 60 (seconds)

Incresea these timeout x 2 or x3 (registry example)

--- Start Registry File ---

Windows Registry Editor Version 5.00

--- End Registry File ---