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

To recap, we are a TMS client with the Altiris agent deployed to 11,000 servers, of which about 20% are UNIX.

We offer our clients a disaster recovery (DR) option, and with that, come the option of having a hot standby server ready to be flipped into production should the need arise.

The issue we came across involves how the server reports its' hostname and domain.

As we know, when the Altiris agent is installed, one process that takes place is the discovery of the hostname/domain on the node and then seeing if it already has a record in the NS database. If it matches, then it will pull down that guid and begin to report under that record. The hostname returns the result of the command 'hostname -s' which is the shortname. That returns all characters (up to a limit of 16) that occur before the first period .

The domain returned is the last two fields that occur before and after the last period.

For example, a server with this as the FQDN: '...

ziggy | 24 Mar 2009 | 0 comments

While tirelessly looking for a method to automatically uninstall Workflow Designer instances found on clients machines, I  stumbled upon this little gem:
C:\Program Files\Altiris\Workflow Designer\Uninstall.exe
Just add an /S at the end for a silent uninstall
I have it setup in a software delivery job to run on a collection that is built using 'All computers' - 'Authorized Designers'.  The latter is a manually updated collection for now since it a small and static (for the most part).  I could also wait for the Operating System Inventory to populate (tablename: Inv_AeX_OS_Add_Remove_Programs), since that contains the contents of Add/Remove Programs and just build a sql query based collection for that.  Which I will probably do in the near future.
Hope this article was helpful.  Short, sweet and to the point.
Thank you.

Raman | 23 Mar 2009 | 0 comments

Well here is a document that covers all the scripts that are required for Microsoft ADS, I hope to be informative for you.



riva11 | 17 Mar 2009 | 1 comment

Maybe in the last year, for different reasons you decided to stop in your organization the deployment of Service Pack updates through Windows Update.
An official Microsoft tool for this task is the Windows Service Pack Blocker Tool Kit,  or a different way is described in my previous post  Block Installation of Windows XP SP3 and Vista SP1.

The Windows Service Pack Blocker Tool Kit allows to temporarly disable this automatic update, but remember only for a limited time.

Now the time could be expires soon, in fact in the Microsoft note release there is the Service Pack update list disabled and the date:

- Windows XP Service Pack 3 (valid until May 19th, 2009)
- Windows Vista...

DParent | 11 Mar 2009 | 3 comments

I updated my golden image with XP sp3 and all the windows updates. Created a new sysprep.inf file. Ran sysprep on the master computer. Shut it down and captured the image.

When I deploy the HII image to the test computers, sysprep starts to run then give me the error "autochk program not found -skipping..." then goes into a continuous loop rebooting.

I tried rebuilding the image from scratch, using the sysprep from sp2 that works good on my current image. Any ideas or advice would be appreciated.

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 | 05 Mar 2009 | 0 comments

After the uninstallation of Altiris Notification Server as per an Altiris KB article, my IIS service did not want to start.

Event viewer displayed the following error:

The World Wide Web Publishing Service service terminated with service-specific error 2147500034 (0x80004002).

Ran the following command to resolve the issue, rebooted server after execution:

regsvr32 c:\windows\system32\oleaut32.dll


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.
riva11 | 09 Feb 2009 | 3 comments

Sometimes it happens. Scenario: During a Windows Office 2007 installation someone thought to shutdown the computer. In this case when you start again the Office 2007 installation, you will see a generic error and the setup will not continue.

I found an article that mentioned a Microsoft Knowledge Base with explained the error and the simple resolution. You have only to delete the rgstrtn.lck file!

In the Knowledge Base article, The 2007 Office suite Setup program will not restart after an initial installation is interrupted there is a detaileddescription with the cause and the workaround about this issue.

In case of some kind of issue and before send a new installation package on the computer, better read this KB srticle, delete the file and go ahead with the ususal installation.