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

BRING | 30 May 2008 | 1 comment

Usually two is better than one. However, in this situation, that is not the case.

When deploying a recently-captured PC Transplant personality, it was discovered that there were 2 Microsoft Excel icons in the Quick Launch Toolbar, as shown in the image below. This was a problem.

To make sure this did not happen again, the PC Transplant personality template was configured to NOT capture Quick Launch toolbar settings. Then, when the personality was deployed, the items in Quick Launch worked correctly.

This only seems to be a problem when migrating settings from Windows 2000 to Windows XP. Migrator, beware!

CondorMan | 23 May 2008 | 5 comments

If you are using WinPE 1.6, you will probably be interested to know that you can enable AClient Remote Control. This allows you to right-click any computer that is running a job in automation so that you can view the progress and troubleshoot any problems that may arise. If you notice that a computer has been stuck in automation for a long time, you can simply remote control the computer to fix the problem.

To enable AClient Remote Control in WinPE 1.6, you will need to edit your Boot Disk Configuration (From PXE or the Boot Disk Creator).

  1. On step 8, you will have the chance to edit the aclient.inp file.
  2. Replace ";PromptRemoteControl=Yes | No" with "PromptRemoteControl=No"
  3. Replace ";AllowRemoteControl=Yes | No" with "AllowRemoteControl=Yes"
  4. Save the changes to aclient.inp
  5. Regenerate your boot environment.

Now you can remote control your clients while they are in WinPE Automation!

ianatkin | 22 May 2008 | 1 comment

I put this on the Altiris Forums a little while ago, but thought it might be useful to place here too.

The link below describes half-a-dozen security vulnerabilities which appear to be only fixed by UPGRADING to DS 6.9 plus the hotfixes Here are the steps I took to remedy the problem.

I've tried to put together a mitigation list. The first draft is below. Can anyone comment on this? A mitigation list would help admins protect their servers now, and allow them to plan the upgrade to 6.9 at a more leisurely pace.

  1. For the SQL-injection vulnerability (exploitable), you have two mitigation options: Follow best practice and ensure that port 80 is heavily firewalled to restrict the Deployment Solution web console...
BRING | 22 May 2008 | 0 comments

Picture this. You get a new computer. It has all of your files and folders from your previous computer, including the cool new wallpaper from the vacation photo you recently were on. A nice, wide screen picture. All of the sudden, you press CTRL-ALT-DELETE to lock your computer to go to lunch, and that nice wallpaper goes into ..... Tiled mode..... Now no one can see that awesome beach you got sunburned on, because there are 24 duplicates of it nicely tiled on your screen. How did that happen?

Well, the nice new computer you have received its personality as a capture from your previous machine. During the capture, migrating your computer from Windows 2000 to Windows XP, the capture template had the checkbox for capturing Active Desktop Settings checked. For some reason, when going between Windows 2000 and Windows XP, this occurs.


BRING | 21 May 2008 | 2 comments

Wouldn't you be a bit frustrated if your My Computer icon disappeared? Well, that can happen.

In capturing a PC transplant Personality from a Windows 2000 client computer and restoring that personality to the newly imaged XP computer, upon inspection, it was found that the My Computer icon, and other commonly found shortcuts were also missing, such as My Documents, etc.

The nasty culprit here is the checkbox in the template creation that allows Active desktop settings to be captured. For some reason, when going between Windows 2000 and Windows XP, this causes that to happen.

Alas, simply unchecking the Active Desktop Settings capture item, and re-running the personality capture, gets the personality correctly assembled. Then the restores work just fine!

riva11 | 20 May 2008 | 6 comments

Many companies are waiting to deploy the Windows XP SP3 and Vista SP1 on their computers. In case you have the same target and use the Microsoft Windows Update or WSUS for the patch management, you will have to block these Service Packs on your computers otherwise will be automatically downloaded.

Some helpful information is in the Ghacks article, at the following link: Block installation of Windows XP SP3 and Vista SP1.

An intersting tip is to create a script with the reg modification and using DS server run on the target client where you need to block this update:

Windows Registry Editor Version 5.00

Remember that you can re-enable the Service Pack deployment on the Windows Update, simply by deleting the registry key. The next reboot...

songs | 19 May 2008 | 0 comments

On page 187 in the DS SP2 Admin guide, it shows an example of the WLogEvent command used with the -ss switch inside double-quotes. While that syntax may work for you, it didn't for me. As expected, you need the switch (-ss) outside of the quotes, and the message you are sending (if spaces are included) to be quoted.

From the manual:

.\WLogevent.exe -c:0 -l:1 "-ss:Finished with the DIR command on %NAME%" 

What worked for me:

.\WLogevent.exe -c:0 -l:1 -ss:"Finished with the DIR command on %NAME%" 

Another curious issue is that when attempting to use WLogEvent to return various return codes from a script, I could only get the task to process the return code correctly if the level (-l switch) was a 3; level 1 and 2 were ignored regardless of the return code provided (-c switch). Perhaps the latter was by...

frankvandebergh | 16 May 2008 | 0 comments

When you want to add a virtual center server to the Altiris Deployment console, you previously would just need the hostname and authentication settings for the virtual center server. As long as you installed the Web Service component in Virtual Center 1.x everything worked just right.

With Virtual Center 2.x, this web service is now more embedded into the product, and using a different default port, 443 instead of 8443.

When connection to Virtual Center from deployment console, make sure to use port 443. You can change the port in the configuration of the VI client.

Also make sure you select "Virtual Center 1.x compatible" under the Web Service options in the options screen of the VI client.

vortex0007 | 15 May 2008 | 7 comments

The best way to install the Altiris AClient as part of the base imaging task, is to have the Deployment Server copy the most recent version of the AClient to the local drive, followed by a call from the Windows XP Cmdlines.txt file to run the installation.

This method ensures your clients always have the latest version of the agent and ensures freshly imaged computers still can be properly managed.

Unfortunately the command line options available for the aclient install are not as wide-spread as they should be.

Here's what the cmdlines.txt should look like to make this successful. And yes, the quotes are required:

"c:\altiris\aclient\altiris-aclient-6.9.164.X86.exe c:\altiris\aclient\aclient.inp -silent -install -scriptedinstall"