Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Configuring
Showing posts in English
Cobra7 | 05 Mar 2009 | 0 comments

Symantec User Migration (SUM) is a great tool to pull a users files, icons, registry settings and Windows settings and put them in a nice and neat little file. They can either then be saved as a backup or installed onto another PC.

The Following back files are what I use to capture and restore a users settings. I keep them out on the network for easy access. Also please note I have SUM installed on the network server and a custom SCMMigrationOptions.xml is being used.

To Capture I use:

@echo off
echo "This will use SUM Wizard to capture a users data for Desktops"
echo "Enter name "
set /p UserName=

echo "Saving to \\Server\share\User_Migration\%UserName%.ump
\\Server\share\SUM\User Migration Wizard\SUMWizard.exe" /action:create...

Antonp | 04 Mar 2009 | 0 comments

I had to do this prior to creating a maintainence plan for a database on my Production box.

When I first tried to create the plan I was given a message that "Agent XPs" are not enabled and that I should run sp_reconfigure.

Run this statement then you can do get on with it:

SQL Query:

sp_configure 'show advanced options', 1;
sp_configure 'Agent XPs', 1;

Cobra7 | 03 Mar 2009 | 9 comments

This is for the Windows (and WinPE) drivers for any PC that uses Intel network drivers 825XX (Such as 82567LM for example) and how to put them into WinPE.

First you will need to download the drivers from Intel, NOT Dell or HP or whatever brand you have.

You can find the site

On the search, type in the network card type (example, 82567LM). Follow the instructions, make sure you get the Vista drivers and not the ones for Windows 64.

The file you should be downloaded should be called "PROVISTA32_v13_5.exe"

Next, you can either use WinZip or WinRAR to extract the files by following this Blog:

Cobra7 | 03 Mar 2009 | 1 comment

Adding Drivers to WinPE (Ghost boot wizard or Ghost Console) .                             

Note: In order to add drivers to the Ghost Console the Ghost Boot Wizard must be used.
  1. Start Ghost Boot Wizard.
  2. Select Windows PE and click Edit.
  3. Highlight WinPE and click Edit
  4. On the right wide will be a button named “Add new driver”, click it
  5. Browse to the .inf file and select it
  6. Name it the name of the driver (i.e. Intel e1000 Pro, Broadcom 57xx)
  7. Select Vista and XP and click Ok.
  8. The driver will now appear on the left side unchecked, check the box next to it.
  9. Click Ok, Ok.
  10. If you wish to make a new boot disk or VP, continue to do so, otherwise click Cancel to leave the program.
Nelo | 27 Feb 2009 | 5 comments

The scenario is a remote PXE server with the following configuration:

Windows 2008 X64 + Windows DHCP server + PXE Server

Clients do not PXE boot without making a change in the PXE Configuration Utility.

Clients PXE booting receive an error message regarding port 4011 and the PXE booting process stops.

The following are the steps to address the issue:

  1. Launch PXE Configuration Utility from the DS Console or from the Start Menu.
  2. Select the PXE Server Tab.
  3. In the DHCP Server Discovery section select "No DHCP server installed on PXE server (Use DHCP port)".
  4. Click Save to commit the changes. Wait until the progress bar disappears.
  5. Click OK to close PXE Configuration Utility.
Note: This only Applies to DS 6.9 SP1.
DParent | 26 Feb 2009 | 4 comments

I would like to figure out the best way to rename computers automatically with unigue names. As of right now, it is setup to give the serial number of the computer. I change the name in the DS console to fit the naming scheme. There has to be a way to start an image job and have it give the computer the correct name and join it to the Domain. As well as any new computers I role out.

Any advice on getting on the right track would be appreciated. I have looked into custom tokens, but having a hard time with it.

Randall Newnham | 25 Feb 2009 | 2 comments

It is possible to run DeployAnywhere when using a PXE service to deliver the Ghost boot package. This method requires use of, and assumes familiarity with, drive mapping. Here are the steps to accompish this:

  1. Create a Ghost Boot CD with the DeployAnywhere option checked.
  2. Copy the contents of this CD to a new folder on a network share. I recommend the name DeployAnywhere.
  3. Create a new PXE boot image, making sure to fill out the Client Settings window with the drive mapping information. If using 3COM Boot Services, you can use the TCP/IP Network Boot Image option and add the settings in the Client Settings window in the Ghost Boot Wizard. If using Windows Deployment Services (WDS), you will need to add the Net Use command with these setting to your Windows Image (WIM). For assistance with this, please contact Microsoft support.
  4. When running DeployAnywhere, note that the command line will need to refer to this path for the windrivers folder....
bkaulins | 25 Feb 2009 | 1 comment

This article is intended to assist Helpdesk Admin automate daily backlog, weekly closed/open incidents, and weekly Individual team members performance reports for email delivery. This article is intended for Helpdesk environments that have numerous queues and need certain team's data sent via email for management review.

In our environment we have numerous queues and the default out of the box reports Altiris provides did not fit our team's needs since the reports show data for the system as a whole. See the queues below.

Our IT management team wanted the following reports that could also...

Antonp | 23 Feb 2009 | 1 comment

I know there was some doubt in the fact that one could copy across all patches to another NS server and it'll be listed as downloaded.

The process is simple.

  1. Install your new NS and configure Patch Management.
  2. Run Qchain and PMImports.
  3. Copy patch files from Updates folder to Updates folder of new NS, if the Updates folder does not exist, create it manually and paste the patches.
  4. Use a small patch i.e MS09-003 to test.
  5. Click download/stage on the patch and review your log - you should see something similar to that in the screenshot.
Andy Tous | 17 Feb 2009 | 0 comments

For those using multiple Dialog Workflow components and using "Form Start" as Workflow Type. If you are asking yourself why isn't my workflow reading the Interaction Setup (first) on my second or subsequent Dialog Workflow components, the below might explain why...

This is the Dialog Workflow component's flow logic:

The Dialog Workflow component always starts with the Event Configuration model, then runs the Interaction Setup (as shown below).

However, if your Workflow Type is "Form Start", the first Dialog Workflow component on your model will read the...