Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Server Management Suite
Showing posts in English
WiseUser | 11 Mar 2008 | 0 comments

Here's an extension to the topic "Installing and Loading Excel Addins with WiseScript" that makes this script even more useful.

We can make the script from that tip more generic so it'll work in any version of Office.

A Small change has to be made to the WiseScript.
Office Version can be found in an HKLM entry under
HKLM\Software\Microsoft\windows\currentversion\app paths\excel.exe
Value Name : Path

Please see the attachment for the script change.

Related article : http://www.symantec.com/connect/article/3607/insta...

CondorMan | 29 Feb 2008 | 5 comments

If you plan on installing Vista Service Pack 1 when it is released (highly recommended), you might want to run the cleanup command afterward.

To do this, open the run dialog (Win-R) and type "vsp1cln.exe" (without quotes) and press enter.

This will remove the ability to uninstall the service pack (so make sure to test everything before running the cleanup), and it will cleanup 1GB worth of data off of your hard drive.

BRING | 21 Feb 2008 | 0 comments

Measure twice and cut once. Sometimes not remembering to do that causes trouble, and has sometimes ruined some beautiful wood stock.

Frequently we do something similar in the Task Server environment when we forget to check the collection references that our tasks are assigned to. Like sending a Shutdown, or Restart task to "All Computers".

While this won't be painless to all end users, we can mitigate it and stop it from hitting everyone, using the following procedure:

  1. 1. Delete the Task from the Console. This may also involve deleting any referenced items as well.
  2. 2. Restarting the Altiris Object Host Service. This will clear the Task Server cache, and allow any deleted jobs to be cleaned and not promulgated to other machines.

It's just that simple. And while it won't be painless for you as the...

BRING | 21 Feb 2008 | 0 comments

Task Server has added some great new capabilities to the Altiris environment. And some solutions are taking advantage of those capabilities. Software Delivery is one of them.

However, it is important to make sure that you have rolled out the Software delivery Agent for Task Server to all of the machines necessary. Otherwise you might just encounter an error like the one below:

Process: w3wp.exe (5152) 
Thread ID: 2376
Module: AltirisNativeHelper.dll
Source: Altiris.ClientTask.Web.RequestSubAgent.Page_Load
Description: Error getting subagent file ( Unhandled exception. Type=System.Exception Msg=Matching agent not found in the database:
AgentName='SWDAGENTFORTS.DELIVERSOFTWARETASKHANDLE', PlatformName='WINDOWS%20SERVER%202003', PlatformType=Production, OSType='WIN32' Src=Altiris.ClientTask
StackTrace=
at Altiris.ClientTask.ClientTaskSubAgent.Load()
at Altiris.ClientTask.Web.RequestSubAgent.Page_Load(Object sender, EventArgs e) )

This occurs when a client...

BRING | 13 Feb 2008 | 0 comments

Naming objects in our Notification Server environment. Seems fairly simple, but the process can be a bit troublesome. Or naming applications, or custom dataclasses. Some times we like to use reserved characters in those names to be descriptive. Characters like($ ; & + , / : = ? @) are reserved characters, specifically to IIS.

These things can cause problems for custom inventories especially. You could see errors like:

Unable to process the file "...\Altiris\Notification Server\NSCap\EvtQFast\Process\INVblah.nse" Moving to "...\Altiris\Notification Server\NSCap\EvtQFast\Bad\AeXException\nseXXX.tmp". Reason: Failed to process NSE System.Xml.XmlException: An error occurred while parsing EntityName.

Certainly, if you can avoid the use of these characters in your naming conventions, that helps.

However, best practices...

kbuller | 06 Feb 2008 | 5 comments

I did a search for "Macintosh" on the Juice site the other day and came up with 4 results... Hopefully this article will be of interest to at least a few people.

The latest release of the Deployment Console supports Macintosh clients but in its current state it is no match for Apple Remote Desktop. I just wanted to share a couple scripts that I use from ARD to make the most out of the Altiris Client for Mac.

Click the "Unix" button on the toolbar of ARD and place these scripts in it.

Refresh Altiris Client Policies

/Applications/Utilities/Altiris/NSAgent/.bin/aex-refreshpolicies

Send Basic Inventory

/Applications/Utilities/Altiris/NSAgent/.bin/aex-sendbasicinv

Run Inventory

Replace -x on the last line with -r for Full, -h for Hardware, and -s for Software

#! /bin/sh...
MarioR | 19 Dec 2007 | 3 comments

While looking for information regarding package server redundancy, I was unsuccessful in locating any references. Hopefully, this posting will fill the missing information gap.

Question:

If a package server was defined for a site and that package server goes down, how will the Altiris Agent clients respond? Original thought was that if the clients were unable to pull from the package server, the clients would fail over to the NS to get their distribution.

Testing Results:

The client tries to download the package from the package server assigned to the site (which was shut down for testing). Since the server was down, initial download was unsuccessful but then client tried to connect again in 3 minutes, then 6 minutes. The check-in time kept doubling until the client checked every 2 hours. From that point on, the...

pragya_gupta | 14 Dec 2007 | 3 comments

Application packagers know there are some vendor MSIs that just can't be edited with Wise but can be edited with ORCA. If, in such a case, we want to add a file to the package, we can't with ORCA because ORCA has limitations and can not compress the file. In these cases, you can follow the steps given below to add the file to the package.

Steps:

  1. Make the .CAB FILE of the File you want to add using makecab command.
    Makecab [Source] [Destination]
    
    

    Where source = path of the file along with file name and Destination = Path where you want .CAB file.

  2. Go to Component Table
    1. Make a component with the name of the file you want to add.
    2. Set the directory column with the path where you want to install the file.
  3. Go to featurecomponent Table
    1. Associate the component made in step 2 with the feature (Complete in case of captured Application).
  4. Go to File table...
R-Vijay | 10 Dec 2007 | 11 comments

Using Wisecomcapture is always the best option to use when registering a DLL. See this article for some background.

But, if there is a case when the DLL doesn't exist in the package and there is a necessity to register a file manually, this tip should prove handy.

To manually register a .DLL using regsvr32.exe in a .MSI package:

Step 1: Go to MSI Script in the WSI project.
Add an Execute Program from Destination custom action after InstallFinalize in the Execute Immediate tab.
The Execute Program From Destination dialog appears.

Step 2: Fill in the following information:
Custom Action Name: <registerdll>
Working Directory: Enter SystemFolder
EXE and Command Line: Enter the full path to regsvr32.exe and the full path to .DLL.
Example: [SystemFolder]regsvr32.exe [WindowsFolder]123.DLL

Step 3: Accept all other defaults and click OK.

...

R-Vijay | 07 Dec 2007 | 0 comments

The internal version number for Windows Vista is 6.0. The GetVersion function returns this version number. The problem is, some applications will return a higher version number. This means trouble. Learn how to steer clear, here.

Symptoms of OS Version

  • Applications that check for OS version will get higher version number.
  • Application installers may prevent themselves from installing the app and apps may prevent themselves from starting.
  • Applications may warn users and continue to function properly.

Mitigation Techniques for OS Version

  • For apps and installers that check for OS version, a Compatibility mode is provided in Windows Vista
  • Users can right right-click the shortcut or the EXE and apply the Windows XP SP2 compatibility mode from the Compatibility tab. This applies multiple shims including "WinXPSP2VersionLie"
  • Better: Apply the shim "WinXPSP2VersionLie"
  • In many cases, applications...