Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Client Management Suite
Showing posts in English
MaggieH | 02 Jan 2009 | 1 comment

You can apply the following command line options to the WSE file. Command line options let you compile as well as set properties.

  • /c file.wse
    Compiles the installation script.
  • /c /s file.wse
    Compiles the installation script silently. You can use this option with the /d option.

WiseScript Installations Command Line Options

You can apply the following command line options to compiled .EXE files.

  • /M
    Runs the installation in manual mode, prompting for system directories (examples: Windows, System).
  • /M=filename
    Specifies a value file for installation.
  • /S
    Installs in silent (automatic) mode with no end user choices.

Uninstall Command Line Options

You can apply the following command line options...

Eshwar | 23 Dec 2008 | 0 comments

Create VBscripts on your fingure tips. Here is the utility that helps you write WMI scripts for system administration, which is provided by Microsoft:

Download it here: http://www.microsoft.com/downloads/details.aspx?Fa...

Note: Genuine OS Validation is required.

Good luck.
Eshwar

Sidd | 16 Dec 2008 | 5 comments

Here is a white paper at www.Microsoft.com, which describes the process of performance tuning a computer running the 2007 Microsoft Office system, or preparing a computer to run the 2007 Office system.

http://go.microsoft.com/fwlink/?LinkId=122086

Thanks
Sid

Sidd | 05 Dec 2008 | 1 comment

Following are the various command line switches that can be used for Microsoft Security Patches.

Available Switches:

  • [/help]
  • [/quiet]
  • [/passive]
  • [/norestart]
  • [/forcerestart]
  • [/warnrestart]
  • [/promptrestart]
  • [/overwriteoem]
  • [/nobackup]
  • [/forceappsclose]
  • [/integrate:<fullpath>]
  • [/log:<fullpath>]
/help
Displays this message

Setup Modes

/quiet
Quiet mode (no user interaction or display)
/passive
Unattended mode (progress bar only)

Restart Options

/norestart
Do not restart when installation is complete
/forcerestart
Restart after...
Mags | 24 Nov 2008 | 7 comments

Ever had an Asset created where the Resource Type is incorrect, or have you had a physical server virtualised, but the Resource Type has remained as Computer instead of Virtual Machine?

Well here's a quick script to change the Resource Type for an individual resource

UPDATE vResource
SET ResourceTypeGuid = '2C3CB3BB-FEE9-48DF-804F-90856198B600'
WHERE vResource.Guid = '9f679247-fc68-4baf-9042-5571cb79ee64' 

In this example, a server, GUID 9f679247-fc68-4baf-9042-5571cb79ee64, has had its Resource Type changed to Virtual Machine 2C3CB3BB-FEE9-48DF-804F-90856198B600.

Common Resource types are:

Asset  B9EE0AB2-AE0E-4867-BF4C-41D4A382163B
Computer  493435F7-3B17-4C4C-B07F-C23E7AB7781F
Monitor  FE46D9CE-B71C-4DE4-B790-242A9EF1A5D3
Network Printer  8E4F62F4-948C-...

WiseUser | 21 Nov 2008 | 0 comments

Return codes are nothing but the errorlevels. The DOS command to determine the return code is IF ERRORLEVEL.

Errorlevels are not a standard feature of every command. A certain errorlevel may mean anything the programmer wanted it to. Most programmers agree that an errorlevel 0 means the command executed successfully, and an errorlevel 1 or higher usually spells trouble. But there are many exceptions to this general rule.

In Wise script the Variable used for getting the return code of an installation is %INSTALL_RESULT%

riva11 | 20 Nov 2008 | 3 comments

Windows System Control Center (WSCC) is a graphic interface that allows you to manage the utilities from Windows Sysinternals and Nirsoft.

This tool is released as freeware and allows you to navigate and execute all Sysinternal and Nirsoft utilities through a friendly GUI. WSCC is only a graphical interface, all tools will be executed on a command line.

For the installation, you will need first to download all or part of Sysinternals and Nirsoft tools, then store together with WSCC in your favorite USB key.

Links:

Deepanshu | 17 Nov 2008 | 4 comments

Some useful information about ATTRIB command which you can use for changing attributes.

Display or change file attributes. Find Filenames.
Syntax

ATTRIB [ + attribute | - attribute ] [pathname] [/S]

Key

+ : Turn an attribute ON
- : Clear an attribute OFF

pathname : Drive and/or filename e.g. C:\*.txt
/S : Search the pathname including all subfolders.

attributes:

  • H Hidden
  • S System
  • R Read-only
  • A Archive

If no attributes are specified ATRIB will return the current attribute settings. Used with just the /S option ATTRIB will quickly search for a particular filename.

Combining the Hidden and System attributes.

If a file has both the Hidden and System attributes set, you...

dougj | 12 Nov 2008 | 1 comment

It is a misnomer to state that Custom Inventory supports certain data types. Within the aexcustinv.exe process, all data is treated as a string type. It is incumbent on the Notification Server dataloader to interpret the data types defined in the column attributes, create the table properly in the database, and validate the incoming data.

So, it is a clearer to say that when creating custom inventory XML scripts, certain data types can be processed by the NS dataloader.

Currently, the dataloader will process the following data types:

Custinv Data Type Converts to SQL Data Type
string nvarchar
int int
dateTime datetime
r4 real
float float
i2...
BRING | 10 Nov 2008 | 0 comments

Standard Reports - You should be able to trust them, especially when they have to do with how complete your patching is in your environment. Normally you can check the reports (Like the "Microsoft Compliance and Vulnerability by Computer" report), and then go set up the correct tasks, and remediate the machines.

If you are like most administrators, you will know what bulletins and tasks you have enabled for distribution. So when you see them show up as vulnerable in the report it becomes very easy to be frustrated (and it could get you in trouble too!). The next thing to do is to be absolutely sure that your reports are accurate. You do this by spot-checking or auditing a few of the individual machines that are reported as vulnerable.

But what do you do when you find that the reports you trusted were wrong? The machines actually were...