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
jamesmax | 16 Apr 2009 | 0 comments

In my search to improve my arsenal of Altiris products, I wanted to know when some of the new 7.0 products were being released. First, I download the installer for the Altiris Client Management Suite. I looked at the requirements page and saw the requirements are “Windows 2003 Server or better”. So, I prepared a Windows Server 2008 (64 bit and 32 bit) VM to test it on. It didn't install on either. After trying it and speaking with technical support, I found out that The Altiris Client Management Suite, as of right now, works only a Windows 2003 Server 32-bit. They said that you should be able to install it on Windows Server 2008 in the near future (probably this summer - time will tell).

Once you run the installer,  it will install the Symantec Installation Manager....

Mohammad Bamya | 16 Apr 2009 | 0 comments

Trying to restore an image to Lenovo M57, the NIC driver related to Intel 82566DM-2 has been added into the WinPE, Ghost finished restoring the image, and when DA starts processing the NIC driver, it return back asking for:
prounstl.exe file from c:\swtools\drivers\ethernet\a2etn00us17\pro1000\

DeployAnywhere only works with drivers that can be installed from their associated INF file, and on the same time it seems that there is another driver availabe under the OS on that image.

As a workaround for that specific NIC, try to delete the oem.inf file related to the NIC under "\Windows\inf\" from the image

jjesse | 15 Apr 2009 | 2 comments

Start your downloads.  If you are a part of the Beta Team you should see CMDB 7 as a part of the available products to download and start testing.

From the email to start beta testing:

We are pleased to announce the beta release of Altiris CMDB 7. Registration for the CMDB 7 beta may be found under the profile tab of the beta portal. We anticipate the beta cycle to run approximately 8 weeks. We look forward to working with you to improve the product toward release.
There are a number of new features with CMDB 7 built on the Symantec Management Platform. The following features have been added or improved:
– Many reports have been rewritten using the new 7.0 reporting engine
– The rest of the reports are available in a legacy mode
Portals in the console
– Customize your own view with web parts
– Tree view of...

Randall Newnham | 27 Mar 2009 | 0 comments

I have seen some issues with hot imaging with McAfee installed and wanted to share the resolution I have found. the primary error I have seen is the "Application Error 503. Connection timed out with Ghost code 19945" in the Ghost Console task logs.Here is how to get around this:

1. Open the Image Create Task, click on the Advanced button in the lower right of the General tab add type this in the "Additional options for Ghost command line" box:


2. On the client and server machines, open McAfee and open the Access Protection feature. edit the Prevent IRC Communication feature (there may be an incoming and an outgoing rule; if so, edit both) and add these exceptions:


Note: The ePolicy Orchestrator is a utility that is often used along with this version of McAfee to make sure that settings are consistent acros a network; the above exceptions will need to be...

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

Before we had the Task solution installed, we were tasked :-) with figuring out a way to get our agents to run a basic inventory and check in to see if there are tasks for it to run immediately and not have to wait till they checked in next time (which may be up to 8 hours later). Well, with the restrictions on ports due to the tightened security in our Data Centers (remeber, we only run our agents on our 11,000 servers) we could not roll out Task even if we wanted to. So my predecessor and I worked on a solution that involved using the ASDK. We came up with this simple batch script that sits on our NS: AltirisASDKNS.exe cmd:ComputerPowerManagement_Collection collectionGuids:{b1463d19-f363-4fff-a64b-be426b627b09} commandsendBasicInventory AltirisASDKNS.exe cmd:ComputerPowerManagement_Collection collectionGuids:{b1463d19-f363-4fff-a64b-be426b627b09} commands:GetClientConfig The first line calls the ASDK 'Send Basic Inventory' command from the Power Management function on all the...

rbrucelee1978 | 19 Mar 2009 | 0 comments

I have noticed that most of the links to sites "designed to help beginners" generally talk about how to create msi's, how to modify these packages or even how to fix some ICE errors. However, these sites do not give beginners any information on very important basic concepts such as Self Healing, Installation Sequences, how to read the logs generated on installation of the msi. These "basic" concepts can help beginners understand things like how these ICE errors occur or say in the even of a failed msi installation where to look in the package based on the information given by the verbose log file.

This site (written by John McFadyen) will provide detailed information on these concepts Windows Installer Blog.

Happy reading!! :-)

Randall Newnham | 19 Mar 2009 | 2 comments

This error can occur when you are trying to automate a Ghostcast session with the -sure switch. What is going on is that the the disk is not specified. In a non-automated Ghostcast session, the user specifies the source (for image cration) or destination (for image restore). When adding the -sure switch, the -clone switch either needs to be included in the boot media, or the disk number needs to be specified in the Ghostcast Server session in the "Client command line options" area. this particularly useful in a PXE deployment environment when the switches -ja=<sessionname> -sure are typically added.

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...

Randall Newnham | 06 Mar 2009 | 0 comments

Ghost Console Clients will not be able to connect to the Ghost Console if the PIX firewall is blocking access to the multicast group ID address of

Configuring the PIX firewall to allow the clients to multicast to the multicast group address, and configuring the firewall to allow the Ghost Console to send unicast UDP traffic to the clients will resolve this.

Alternatively, using the Ghostcast method with either the switch -JADDR=<serveripaddress>, or by entering the server's IP address after entering the session name will work. This bypasses the need for a multicast communication for client identification.