Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Deployment Solution
Showing posts in English
johnquinn | 19 Jun 2008 | 2 comments

By now, many people have migrated their users over to Office 2007. I did at my company for two main reasons. The first was to standardize everyone on the same platform and the second was to prepare for the upcoming Exchange 2007 deployment.

From our end, this was a very successful migration, but it ended up causing some problems. Our parent company, is still on the Office 2003 suite. They have plans to upgrade, but that is several months down the road for them.

So the problem is if our users save a document and send it to them, they cannot read it unless they download the Compatibility Pack from Microsoft.

So I was tasked to come up with a solution that would get our users saving in the Legacy format at least until the parent company migrates.

I initially came up with 2 options:

  1. Tell our users to remember...
CondorMan | 18 Jun 2008 | 0 comments

If you've ever had a domain join fail, you can understand how frustrating it can be to troubleshoot. There is a log file that will make it much easier to figure out what is wrong.

  • Open the file C:\WINDOWS\Debug\NetSetup.log.
  • Go to the very bottom of the file and find the last "NetpDoDomainJoin: status:"
  • If it is not 0x0, then the domain join failed and the code listed instead of 0x0 is the reason it failed.
  • Now, look at each previous line in the file until you come across the last line in the file that returned the same failure code as your Domain Join.
  • You have found the step of the domain join that failed and the reason it failed.
CondorMan | 18 Jun 2008 | 1 comment

Sometimes a Windows Executable, Script, or Command will fail with an error. What does that mean?

While there is no enforced set of error code meanings, most executables and all system commands follow a standard definition of error codes.

You can find out the meanings by viewing Microsoft's list of Windows Error Codes and their descriptions here.

You might want to add that link to your favorites.

CondorMan | 18 Jun 2008 | 0 comments

Have you ever wanted to start, stop, delete, create, or configure a service in your batch script? The "SC" command will allow you to do this and more.

Here are a few examples of how you can use this command:

Start a service sc start ServiceName
Stop a service sc stop ServiceName
Delete a service sc delete ServiceName
Create a service sc create ServiceName binPath="C:\Program Files\InstallDir\Service.exe" start=auto
Configure a service sc config ServiceName <options>

For more information about the settings you can make when creating and configuring services, go to a command prompt and type "sc create /?" and "sc config /?"

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 | 09 Jun 2008 | 3 comments

Have you ever needed to modify the registry of an image, so you download the image to a computer, make the registry changes, and re-upload the image? Well, there is a much easier way!

The Symantec KB Article #2584 will give you step-by-step instructions about how to extract the registry of an image, modify it, and inject it back into the image.

This will save you alot of time and effort.

CondorMan | 06 Jun 2008 | 4 comments

Sometimes a Windows Installer will fail with an error 16xx. What does that mean?

You can find out by viewing Microsoft's list of Windows Installer Error Codes and their meanings here. You might want to add that link to your favorites if you manage a lot of .msi installs.

CondorMan | 05 Jun 2008 | 1 comment

If your workstations are using the NTFS file system, you can use COMPACT.EXE that is included with Windows to compress files with a certain extension. For example, to compress all of the .CHM files (which are rarely used), use the command: COMPACT /C /S:C:\ *.CHM

Here is a list of all the available parameters:

COMPACT [/C | /U] [/S[:dir]] [/A] [/I] [/F] [/Q] [filename [...]]

/C Compresses the specified files. Directories will be marked so that files added afterward will be compressed.
/U Uncompresses the specified files. Directories will be marked so that files added afterward will not be compressed.
/S Performs the specified operation on files in the given directory and all subdirectories. Default "dir" is the current directory...
CondorMan | 05 Jun 2008 | 2 comments

I just learned that you can enable MSI logging so that if your installer fails with an error you can see where the MSI failed.

To enable MSI loggging:

  1. Open Regedit.
  2. Go to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer.
  3. Create a new Reg_SZ value named "Logging" with the value "voicewarmup".

While "voicewarmup" is easy to remember, it actually signifies all of the different options that you want to enable.

Here is the complete list of options:

v Verbose output
o Out-of-disk-space messages
i Status messages
c Initial UI parameters
e All error messages
w Non-fatal warnings
a Start up of actions
r Action-specific records...
Nelo | 03 Jun 2008 | 2 comments

There are times where PXE booting seems to take a long time especially with WinPE. After making some changes to the MTU (Maximum Transmission Unit) I was able to download WinPE 1.6 and 2.1 under 20 seconds.

Note: this depends in the speed of the network; all my tests are in a fast network.

Launch PXE Configuration tool and select the Multicast tab.

Change the Packet Size from 768 to 1456. Now this works OK for me and I have seen reports that others had success with this as well. If this does not work revert back to 768.

Finally, click save then...