Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Windows
Showing posts in English
piyushnasa | 19 Sep 2008 | 0 comments

RegSpy is a third party tool which is very helpful at times when most of the registry capturing tools like ComCapture and others, fail. I have seen this tool get registry when ComCapture fails to retrieve registry.

You can download RegSpy from site:

Here is how it works:

To get the registries, you need to open a command prompt, drag drop regspy.exe to command window and give .dll/ or .ocx file as the command line argument. It then loads the .dll or .ocx and looks for DllRegisterServer to call. It then redirects the HKCR and HKLM registry entries to HKCU\Software\Substitute\Registry\(filename)\HKCR and HKCU\Software\Substitute\Registry\(filename)\HKLM

nac | 22 Aug 2008 | 1 comment

Well this is an intresting tip while moving from XP to Vista. When we launch the Help file in Vista, Help file (.hlp) may give you the following types of errors.

  1. An error like this means the particular Help file is not compatible to work on Vista. You need to apply a Help patch. So unless and until you apply a patch you will not be able to open the Help file.

    You can download this patch from following link.

  2. It doesn't stop there. After applying the patch you open Help again and this time you may...
Dan Waksman | 20 Aug 2008 | 3 comments

If you are beginning to test Vista, and are looking into the various activation methods, you will quickly learn that KMS activation requires a minimum of 25 PCs. Therefore you may need to begin testing with a MAK key and later switch to activating against a KMS server.

In order to switch back to KMS activation, use the following command lines for Vista Enterprise:

slmgr.vbs /ipk VKK3X-68KWM-X2YGT-QR4M6-4BWMV
slmgr.vbs /skms SERVERNAME
slmgr.vbs /ato

For Vista Business, substitute the key with YFKBB-PQJJV-G996G-VWGXY-2V3X8. See for more details on Volume Activation 2.0.

If you need to switch back to a MAK key,...

Dan Waksman | 06 Aug 2008 | 1 comment

If you have created a Vista image using a Scripted OS Install task, then you most likely left the command line to install the DAgent: C:\DAgent\DAgent.msi /quiet server_tcp_addr=%DSSERVER% server_tcp_port=402 scripted_install=1 LAUNCHUI=FALSE

However, you have now created an image that will connect the DAgent to whatever Deployment Server the image was created on. If you are using multiple Deployment Servers and are trying to use the same image, obviously this will be an issue. To work around this, I created a task to run immediately after a Distribute Image Task in WinPE pre-boot automation, which switches the DAgent to the correct Deployment Server, by modifying the registry:

REM Point DAgent to correct DS

reg load HKLM\TEMP c:\windows\system32\config\software
reg add "HKLM\TEMP\Altiris\Client Service" /v DSIp /t REG_SZ /d "%...
Dan Waksman | 05 Aug 2008 | 0 comments

When adding a Create Disk Image task for a Vista image and modifying the advanced sysprep properties, selecting "install additional drivers" and adding a path will allow drivers to be injected into the image.

However, the problem with this, is that you will be prompted for unsigned drivers after pulling down the image with a Distribute Disk Image task. To get around this, I created a custom InstallDrivers.xml in the Deploy directory:

<?xml version="1.0" encoding="utf-8"?> 
<unattend xmlns="urn:schemas-microsoft-com:unattend">...
R-Vijay | 25 Jul 2008 | 3 comments

This very good article will help you understand Windows Vista better. There is a lot more to talk about. Once you go through that article, I believe your complaints would be reduced for sure!

You can obtain the article from

Harsh Mokal | 23 Jul 2008 | 0 comments

To protect sensitive data on your PC, encryption methods always helpful.

BitLocker Drive Encryption is security feature in the Windows Vista operating system that provides protection for the operating system on your computer and data stored on the operating system volume.

BitLocker ensures that data stored on a computer running Windows Vista remains encrypted even if the computer is tampered with when the operating system is not running.

I searched on net to find how to configure it & found a good article. Links are as follows.


R-Vijay | 26 Jun 2008 | 3 comments

To avoid UAC prompts for applications on launch, there exists a manifest file which contains key information on the privileges. Many times, these manifest files are present along with the executable in the same directory. For example: Altair.exe will have a manifest file called Altair.exe.manifest in the same directory. There can also be cases where the manifest is embedded in the exe itself. In this case, identifying the launch condition for this exe involves a lot of research.

Here is a simple executable which will help research those launch conditions.

Sigcheck.exe is an executable from the Sysinternals team that enables you to check whether a file has been digitally signed. The -m switch allows you to view any manifest within the file. All we need to do is run this sigcheck.exe with -m switch along with the executable, the full manifest will be displayed on the command prompt window.

If the XML manifest is going to prompt an elevation then there will be a...

tbowman01 | 16 Jun 2008 | 2 comments

After a week of reading many posts about problems with the new Optiplex 755 and the new Intel 82566 DM-2 network cards I have finally found a solution. I have verified that using this driver that the network card works in both Windows Deployment Server and Altiris Deployment Server. I have not tested BartPE.

  1. Download the latest Intel NIC driver from for the Optiplex 755
  2. Extract the file, current version R162323.exe or newer, copy the file from c:\dell\drivers\R162323 to c:\ and rename the folder to 755-NIC-Driver
  3. Then use imagex to mount the boot.wim file
    Imagex /mountrw c:\boot.wim 1 c:\WinPE_x86\mount
  4. Add the drivers to the mounted boot image
    Peimg /inf=c:\755-NIC-Driver\*.inf c:\WinPE_x86\mount
  5. Unmount the boot image and commit changes
    Imagex /unmount /commit c:\WinPE_x86\mount

I am using WinPE 2.1 vista build boot.wim, therefore, the driver that I loaded was the Vista32 e1e6032.inf...

CondorMan | 18 Apr 2008 | 3 comments

PowerShell is the new powerful scripting language created by Microsoft. You can install it to Windows XP and above and it is included in Windows Server 2008.

Here is how to run a PowerShell Script through Deployment Server.

  1. Create a new job.
  2. Add a Copy File task
    • The source path points to MyScript.ps1 on the Deployment Server.
    • The destination path is .\MyScript.ps1
  3. Add a Run Script task as the following:
    powershell -command "& { .\MyScript.ps1; exit $lastexitcode }"
    set ret=%errorlevel%
    del .\MyScript.ps1
    exit %ret%