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 | 13 Sep 2007 | 5 comments

Here's the scenerio: You have a system file that needs to be installed to the System32 folder. And, you have several HKEY_CURRENT_USER registry keys containing configuration information.

This causes problems since the installation writes a file to the System32 folder, which is locked down for non-administrator users. Read on for the solution.

Here are your options:

  • Require an administrator to install the application. While this places the file in the System32 folder, the registry keys install with the administrator's profile rather than the end users.
  • Split the install into a per-machine and per-user installation. This creates two installations to track and requires the administrator to run each per-machine installation and each user to run the per-user installation.
  • Create one installation that...
riva11 | 23 Aug 2007 | 0 comments

The original article SVS 2.1 HotFix 2 Available , submitted by Scott Jones can be read by here .

La HotFix 2 per Software Virtualization Solution 2.1 è stata rilasciata nel sito Altiris Knowledgebase. Questa HotFix include numerose fix riguardanti la stabilità ed è raccomandata per tutti gli utilizzatori di SVS . Questo è un aggiornamento cumulativo, che include tutti gli aggiornamenti a partire da HotFix 1.

Dettagli:

  • Workaround per difetti nei registri Microsoft che possono causare un blue screen quando sono chiamate certe funzioni di registro.
  • Fix per un problema di compatibilità di IIS -- Nota: IIS non è ancora supportato in un layer SVS ! Tuttavia, una prossima release di Wise Installation Studio richiede che SVS e IIS siano installate assieme nello stesso PC
  • Fix in caso di memory leaks che possono causare un anomalo supero del tempo nelle...
BRING | 22 Aug 2007 | 0 comments

Many people use Patch Management to meet all of the patching needs. Operating Systems, Office installations, and other applications all can get the benefit of Patch Management's capabilities.

When patching MS Office, frequently, access is required to the source files that were used during the install, in order for the patches to apply correctly. But what about other applications, such as MS Visio, and MS Project? Do they have the same requirements?

Well, KB article 37609 may not answer the questions for all other MS applications, but it does give the Visio and Project scoop. See the link here for the answer:

https://kb.altiris.com/article.asp?article=37609&p=1

SK | 20 Aug 2007 | 0 comments

Patch Management Solution sometimes encounters problems when additional updates are created by Microsoft or when revised versions are released or even when the NS fails to download all of the updates the first time.

These scenarios will prevent you from creating a SW Update Task for the Bulletin until the missing updates have been downloaded.

I have quite frequently experienced that when using the "Recreate Packages" option, the NS still fails to download one or two of the updates.

When this happens, I simply disable the Bulletin, and then stage it again, as this always downloads all updates successfully.

WiseUser | 16 Aug 2007 | 3 comments

We use deferred custom actions to perform actions and manipulate system files. Here's an example where I learned something new about these actions and Installshield \ VB Script.

One of my applications needs to append a value to the Autoexec.bat file, and we use VBScript to do this work. I wrote a custom action to append a value in the .bat file. Since the file is present in "c:\" I used "WindowsVolume" but it was not recognized in the deferred custom action. This is because deferred custom actions doesn't recognize installer properties like SourceDir or WindowsVolume.

To solve this issue, here are the steps we took. This is not an issue if you use WiseScript. But not all projects use WiseScripts.

  1. Create a custom action which has embedded VB code in it that appends the value to the .bat file. Let the custom action name be "APPBAT" and set the custom action as deferred system context and leave the sequence blank -- to be modified later
  2. Create...
robertser | 06 Aug 2007 | 1 comment

When new computers are placed into Altiris it may take up to 24 hours for the system to get all of its patches and inventories completed. This is usally due to collection update times and long configuration update times (6+ hours).

There is an easy way to speed this whole process up and not effect the overall performance of your NS.

  1. Create a collection called "Computers Discovered 48 hours". Using the SQL code below it will contain PCs that are discovered in the last 48 hours.

    SQL Code:

    SELECT vr.guid    
    FROM vresource vr     
    join vComputer vc on vr.guid=vc.guid   
    join item i on vr.guid=i.guid    
    WHERE DATEDIFF(day, i.CreatedDate, getdate()) <= 2
    
    
  2. Create a duplicate of the collection "All Windows Desktop Computers Collection (excluding Package Servers)".
  3. Under the Altiris...
BRING | 03 Aug 2007 | 0 comments

What a frustration. You click on your Inventory task and all of the sudden you see the following error: "Error when node clicked: An unexpected exception has occured during CreateInstance."

Read on for the remedy.

Well, the solution to this issue is not a simple as you might think. KB Article 36366, found at https://kb.altiris.com/article.asp?article=36366&p=1 gives the best solution to making sure that you database is ready to handle to load that inventory solution can apply.

The bulk of the resolution to this issue comes...

riva11 | 30 Jul 2007 | 1 comment

During remote installation or will running a command script on a remote computer, I prefer to hide as much as possible from the remote computer's display. I've found that even if software installation can be done in a silent mode, there are some things, like OS scripts, that are not hidden. Here are a few tips to make sure you aren't exposing too much to prying eyes.

To hide some time jobs running on the user desktop, I found an easy way and is send a lock workstation command. Using the following method during an installation the only screen displayed is the logon screen. Nothing else is shown.

After this command the user does have to log in again. But it does enable you to run short scripts or use off-hours periods to run your scripts without them appearing on the screen.

Here is the script:

@Echo off
rundll32.exe...
riva11 | 10 Jul 2007 | 2 comments

During Windows client preparation, most of the corporate programs I work with create a shortcut icon on the user's desktop.

I prefer to maintain a computer clean of programs used infrequently. For example, Adobe Reader and other viewers normally are executed from a folder or e-mail attachement, not by launching the program from a shortcut on the desktop.

For this reason in my installation process I have a list of shortcut icons to remove from the desktop.

The traditional way to remove a shortcut icon is to drag it to the Recycle Bin or press the Delete key.

But I've found using a process is the best way to automatically remove these pesky icons for you.

In this example I decided to remove the PDFCreator shortcut. It is normally created during installation in the All User Profile folder.

In the DS console is...

dmorrison | 09 Jul 2007 | 1 comment

Sometimes it's desirable to create 4 collections for inventory tasks so software audits only occur on a particular day for 1/4 of the computers in the environment without dealing with the random execution of AexRunControl. Or your CIO wants to evenly distribute a software delivery over 10 days to reduce risk and you would like to avoid creating 10 dynamic collections.

One of the challenges we often face in Notification Server is creating collections that evenly divide computers into several groups to distribute inventory processing or software delivery.

The SQL script below provides a simple way to create a dynamic collection which will be roughly 1/4 of the computers in your Notification Server. It contains 2 variables: @Groups and @GroupNumber. To create another collection for the different 1/4's of your computers, change the...