Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
ianatkin | 25 Jul 2008 | 6 comments

Have you ever cloned your DS jobs for copying to various computer build folders, and then been frustrated when you have to locate each copy later to update them? If so, then Deployment Solution job shortcuts are for you, so read on.

Introduction

The idea behind Deployment Solution shortcuts is simple. You maintain one master job, and when you want to create a copy you instead create a job which is simply a reference the master.

To illustrate, let's look at a sample jobs pane which is causing you, the DS Admin, some grief.

Above we can see a typical looking DS jobs pane -here we have build folders for various types of computer defined by...

marcoads | 22 Jul 2008 | 3 comments

How do you use the name of a Computer Group within the DS console as a task condition? This tech tip will show you how. Note that this will only work with Deployment Solution 6.5, 6.8, and 6.9.

Create a Task Condition and use a User Defined Token with the token condition:

%#*"Select group_name from computer_display where computer_id=%ID%"%

This token is evaluated at run time when the agent is connected.

WiseUser | 21 Jul 2008 | 9 comments

Darwin Descriptor registry is an encoded value used by Windows Installer under registry like HKEY_CLASSES_ROOT\Excel.Sheet.8\shell\Open\command\

The encoded data in "Command" string value resolves to a specific product, component and feature.

Windows Installer decodes the specific component and checks its presence on the system. If the component is not available it triggers the MSI product repair.

This is one more reason why a Vendor MSI should never be captured. As this encoded information (if captured) will be an invalid reference. Normally this information in an MSI is stored as Advertised CLSIDs for the particular file.

trb48 | 21 Jul 2008 | 0 comments

A few weeks back I needed to figure out how to add some computers to our domain. I did not want to go to every computer. There are a couple of ways to add a computer to the domain. The first is a VBS script. I am not sure where I found this script, but here it is:

Const JOIN_DOMAIN       = 1
Const ACCT_CREATE       = 2
Const ACCT_DELETE       = 4
Const WIN9X_UPGRADE      = 16
Const DOMAIN_JOIN_IF_JOINED  = 32
Const JOIN_UNSECURE      = 64
Const MACHINE_PASSWORD_PASSED = 128
Const DEFERRED_SPN_SET    = 256
Const INSTALL_INVOCATION   = 262144

strDomain  = "DOMAIN"
strPassword = "PASSWORD"
strUser   = "USERNAME"

Set objNetwork = CreateObject("WScript.Network")
strComputer = objNetwork.ComputerName

Set objComputer = GetObject("winmgmts:{impersonationLevel=Impersonate}!\\" & _
  strComputer & "\root\cimv2:Win32_ComputerSystem.Name...
riva11 | 08 Jul 2008 | 2 comments

There are some tips in Linux commands that can be useful also for Juice users in the Windows CMD environment.
For example one of my favorites is the file and directory name completion. The explanation is easy, in Unix shell, you can type the first letters and press the TAB key and it will completed with the first file/folder.

The same tip in Windows environment is turned on by default (Why?). IT admins can have many benefits and speed up typing commands in Command Console. In fact sometimes, change folders or copying the right file name is difficult. But the solution is easy, just enable this feature, as already previously stated, by default it is disabled.

  • Select Start , Run and type REGEDIT
  • Navigate to the HKEY_CURRENT_USER\Software\Microsoft\Command Processor hive.
  • Change the DWORD value "...
MBHarmon | 27 Jun 2008 | 0 comments

In some environments, or for some ticket types, there always needs to be an Asset. After all it doesn't make much sense to have an install software request without a computer seleted. For those options you can create a validation rule that will require this option.

If creating your validation rule for something such as as "Request" Type just enter it with the following parameters:

Name: Asset must be selected

Comment: Requires workers to enter select an Asset when none has been selected.

Display this message: Please select a valid Asset. The Asset NONE is not valid for requests.

When: Every time incident is saved

When ALL of these are TRUE
 "Type" is not equal to "Request"
 "managed_object_id" is the same as "1"

To enter the last line of that...

MBHarmon | 27 Jun 2008 | 0 comments

In some environments, or for some ticket types, there always needs to be a contact. For those options you can create a validation rule that will require this option.

If creating your validation rule for something such as a "Request" Type just enter it with the following parameters:

Name: Contact must be selected

Comment: Requires workers to enter select a contact when none has been selected.

Display this message: Please select a valid contact. The contact field is blank.

When: Every time incident is saved

When ALL of these are TRUE
 "Type" is not equal to "Request"
 "workitem_contact_id" is the same as "1"

To enter the last line of that parameter just use an <Advanced Condition>

mboggs | 25 Jun 2008 | 4 comments

When using My Helpdesk Console (winuser), sometimes end users try to type their entire issue in the Title field, rather than the Comments field.

I created a Validation Rule which requires the end user to include a Comment when submitting an incident using My Helpdesk Console (winuser).

In addition to this, we renamed the label on winuser from Title to Summary. We had many end users putting their job title in that field, not knowing any better.

Here is the validation rule:

Name: Blank comments not allowed for guests

Comment: Requires guests to enter a non-blank comment.

Display this message: Please enter a comment

Log to Notification Server: If no user interface present

When: Every time incident is saved

And: When ALL of these are TRUE
"Comment" is the same as...

CondorMan | 20 Jun 2008 | 1 comment

I just discovered a nifty utility in the eXpress share called wndctl.exe. You can use it to lock the keyboard and mouse prior to any install/script and unlock it later. It can also activate, minimize, maximize, restore, hide, show, flash, close, disable, enable, tile, cascade, center, move, and resize window(s).

wndctl.exe can be found in any of the following places (in x86 and x64 versions):

  • Bootwiz\platforms\Winpe\x86\Optional\Boot
  • Bootwiz\platforms\Winpe\x64\Optional\Boot
  • Bootwiz\platforms\Winpe2\x86\Optional\Boot
  • Bootwiz\platforms\Winpe2\x64\Optional\Boot

The syntax for wndctl.exe is:

wndctl <command> [<"window title text">] [<n>]

<command> is the command to perform, and is one of the following:

-activate Make the...
CondorMan | 20 Jun 2008 | 0 comments

I just discovered that you can customize WinPE using the prestart and startup folders.

Here are some things to keep in mind when using the folders:

  1. All batch files you add to the prestart folder are run just before the network loads.
  2. All batch files you add to the startup folder are run just after the network loads.
  3. The batch files are run in alphabetical order.
  4. If your batch file launches another batch file, be sure to use the call command, or it will not return to the WinPE startup batch.
  5. If your batch file launches a program that will stay running be sure to use the start command, or it will hang and the WinPE boot will not continue.