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
CondorMan | 24 Sep 2008 | 0 comments

TCPView will display which active and listening sockets an application has created. This can be helpful for troubleshooting network applications.

More information can be found at

CondorMan | 23 Sep 2008 | 1 comment

If you ever need to script the removal of an application or need to run an install or upgrade that requires the application to be closed, you can use PsKill to kill all the open processes of a certain file so that you can be sure the task will complete successfully without any files being locked.

PsKill will terminate a local or remote processes. You can find out more at

CondorMan | 23 Sep 2008 | 0 comments

Have you ever noticed that even after a clean install of Windows your pagefile is fragmented and the disk defrag utility will not help.

PageDefrag will defragment your paging files and Registry hives. Leaving your system at peak performance.

You can find more information at

CondorMan | 23 Sep 2008 | 0 comments

Filemon lets you see all file system activity in real-time.

It is useful to discover file requirements for a certain application or to discover the location of files being written to.

You can find more information about this tool at

erikw | 23 Sep 2008 | 2 comments

When you install Deployment Solution on a network where other software is already running that uses PXE, you can get in serious trouble.

I found a document that explains what to do when you want to install Deployment Solution on a network that is already running Ardence.

Read it, and get started.

BRING | 17 Sep 2008 | 0 comments

When using Deployment Solution to roll out new IBM x3850 servers, the Linux PE environment received an interesting error when attempting to boot:

'badness in do_exit at kernel/exit.c'

This particular server had 16 processors. Apparently the Linux kernel configured for this boot process was unable to correctly address multiple processors.

Fortunately, this was a fairly simple fix. Deploying the image was not really a multi-processor critical operation. By adding the 'maxcpus=1' statement, as defined below, the kernel was then configured to only operate using one CPU. This resolved the problem.

In the MISC folder


CommandLine="root=/dev/ram0 rw ramdisk_size=32768 maxcpus=1"


default linux
label linux
 kernel linux
 append initrd=rootfs.gz root=/dev/ram0 rw ramdisk_size=262144 quiet...
Antonp | 12 Sep 2008 | 3 comments

As we all know RDeploy gives us the function to convert an already caputered image.img file to image.exe file.

Recently I created a DVD bootdisk with the image spanned over multiple DVD's. I had an .img image that I used in the process.

The WinPE booted fine, but then prompted me to enter the last disk the whole time, even if I did enter the last disk, nothing happened. I then proceeded to load RDeploy in the GUI mode and browse to the image location, cool I found it, but was unable to load it as RDeploy said it cannot access that image file. Bummer....

So then I converted that same .img file to an .exe file on the DS in "Image Explorer", went through the same process and the same end result.

We then thought that the conversion process might have corrupted some files or not properly converted the .img to .exe....

jjesse | 12 Sep 2008 | 0 comments

Just a quick note, that if you are imaging and deploying SUSE Enterprise Linux on VMWares's ESX server you need to be on the latest version for it to work correctly.

If you are running 3.1 when you deploy the images, eth0 does not come active after the reboot and you must manually reconfigure it through YaST.

If you upgrade your ESX box to 3.5 the deployment of the image functions correctly.

dnorris | 10 Sep 2008 | 10 comments

BIOS updates can be automated along with your standard deployment routines. A single job can be used regardless of the model being deployed.

We'll first make use of the Condition feature on DS jobs and then of a command-line parameter available on Dell BIOS update files.

Create a new job in your Deployment console, click the Setup button in the Condition section and create a new condition. Name the new condition to describe the computer model.

This example shows the condition for a Latitude D630.
For the...

CondorMan | 29 Aug 2008 | 3 comments

If you ever need to script NTFS permission changes, SetACL is a powerful alternative to CACLS. Here is a command line that will use SetACL to grant full control to the Administrators and System accounts on folder and all subfolders:

SetACL.exe -on "C:\Program Files" -ot file -actn ace -ace "n:administrators;p:full" -ace "n:system;p:full" -actn clear -clr "dacl,sacl" -actn rstchldrn -rst "dacl,sacl"