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
nravenscroft | 22 Jul 2008 | 0 comments

Last time we covered adding a collection picker to your reports. In case you missed it you can find it here. I know after reading the prior tip you were excited beyond belief, and happily adding collection pickers to all your reports.

That is until you realize that you have to select a collection each and every time you want to run the report, and most of the time you end up selecting the same collection. Fear not, because today I'll show you how to set the default collection.

First off we need to pick a collection. Let's go with the All Computers collection. We'll need to browse to the collection in the NS console right-click it and choose properties.

...
marcoads | 21 Jul 2008 | 0 comments

Want to use WiseScript to force a reboot, but do not know how? These steps can help you do just that. This tip will tell you the commands to use in order to reboot with WiseScript.

To create a Force Reboot:

  1. Go to the Build Settings page under Build Options.
  2. Check the check box named No Reboot Message During Silent Installs. If you run the install in silent mode, the system will reboot for you.

Another way of forcing a reboot without running your main install in silent mode is to execute a second executable in silent mode. You will need to create a second executable with Wise. Create a script containing one line of code using the Set Variable action in the Script Editor.

In the Set Variable dialog, enter RESTART in the Variable field. Enter S in the New Value field and click OK. Go to...

trb48 | 18 Jul 2008 | 5 comments

There are several different ways to update Windows computers. Most people use Windows Updates. That doesn't work well in a corporate environment, especially if you need to make sure that the computers get updated. Another useful way to update your computers is to use Altiris Patch Management. There have been a few great articles on Patch Management lately:

You can also download...

nravenscroft | 18 Jul 2008 | 1 comment

The Item picker is a great tool for extending the functionality of reports. More specifically the collection picker allows you to dynamically manage the scope of your reports.

In this article we'll go over how to create and use a collection picker.

Go ahead and click finish and then open the edit windows for the report.

Once in the Edit window we'll need to create a couple parameters, so click the New Parameter button and create a basic string parameter called AppName be sure to click the box for to Prompt User, type a friendly name and set the default...

marcoads | 18 Jul 2008 | 0 comments

Now that you have created a custom inventory, how do you know which SQL tables are storing the data? This tip will show you how.

Note: This only applies to Notification Server 6.0 SP3 and Inventory Solution for Windows 6.1 SP3.

At the time a Custom Inventory file is created, the Altiris administrator is responsible for defining the schema that will be used by SQL to create the primary table that will store the data being captured. The InventoryClass name provides the table name and each AttributeType correspond to the names of the columns that will be used to create the table.

A visual list of the InventoryClass Name and the column names are available by opening the Notification Server Console, and navigating to the following location:

Configuration tab > Configuration > Resource Settings > Default...
marcoads | 15 Jul 2008 | 0 comments

Configuring Patch Management 6.2 can be a big hassle. This tip will give you a quick summary on how to configure this program. Note that you do need to set up the computer collections and add the needed computers for each.

First, you need to go to Configuration tab > Solution Settings > Software Management > Patch Management > Windows > Default Software Update Agent Configuration and enable the default software update agent configuration policy, and point it to the collection that is to be updated automatically. This will set the schedule for the updates to download and install, and to provide the schedule for rebooting, so the computers do not reboot after each update or at sporadic times throughout the day. This policy can be cloned by right-clicking in the left pane and cloning, but...

Eshwar | 07 Jul 2008 | 14 comments

You can manually delete temporary files and folders from the following locations:
[C:\Documents and Settings\<username>\Local Settings\Temp]
[C:\Documents and Settings\<username>\Local Settings\Temporary Internet Files]

You can ignore the above method since there is a smart way to do it. Just execute the following script and you are done.

'=============================================
'File Name: DELETE_TEMP_FILES.VBS
'Comment: This script will delete all temporary files and folders
'=============================================

On Error Resume Next

'Declare variables
Dim fso 
Dim oFolder1
Dim oFolder2
Dim oFolder3
Dim oSubFolder1
Dim oSubFolder2
Dim oSubFolder3
Dim colSubfolders1
Dim colSubfolders2
Dim colSubfolders3
Dim oFile
Dim userProfile
Dim Windir

'Set up environment
Set WSHShell = CreateObject("WScript.Shell")
Set fso = createobject("Scripting.FileSystemObject")
userProfile = WSHShell.ExpandEnvironmentStrings("%userprofile%")...
CondorMan | 26 Jun 2008 | 4 comments

There are a few ways to have a batch script wait for a number of seconds. The simplest and most widely available without any additional programs is to use the ping command.

The following is is an example... PING!

ECHO Waiting 5 seconds
PING 1.1.1.1 -n 1 -w 5000 > NUL

CondorMan | 25 Jun 2008 | 0 comments

OSQL is a flexible command-line utility that allows you to run SQL Queries, Commands, and Stored Procedures from the command-line or through a Batch script.

In order to run OSQL, you can either run it on your SQL Server or copy OSQL.EXE and osql.rll to a location that a client machine can run them from.

The syntax for OSQL is:

usage: osql       [-U login id]     [-P password]
 [-S server]      [-H hostname]     [-E trusted connection]
 [-d use database name] [-l login timeout]   [-t query timeout]
 [-h headers]      [-s colseparator]   [-w columnwidth]
 [-a packetsize]    [-e echo input]    [-I Enable Quoted Identifiers]
 [-L list servers]   [-c cmdend]      [-D ODBC DSN name]
 [-q "cmdline query"]  [-Q "cmdline query" and exit]
 [-n remove numbering] [-m errorlevel]
 [-r msgs to stderr]  [-V severitylevel]
 [-i inputfile...
CondorMan | 18 Jun 2008 | 1 comment

Sometimes a Windows Executable, Script, or Command will fail with an error. What does that mean?

While there is no enforced set of error code meanings, most executables and all system commands follow a standard definition of error codes.

You can find out the meanings by viewing Microsoft's list of Windows Error Codes and their descriptions here.

You might want to add that link to your favorites.