Blog Posts tagged with Systems Management

Ask a question

KACE SMA - Adding Clients to AD Groups

Hi All,

this is a little AddOn to my previous post: KACE SDA - Adding Clients to AD Groups during deployment
This blog will focus on an ongoing management of AD security groups. 

First i have to say the main script is written by OneScript Team.

The idea here is to use KACE SMA to have an sheduled or an adhoc script wich will assign devices to specific AD securitygroup(s). 
First we will create an online KScript like this: 
sma_aag_001.png

After that we have to decleare on which device(s) it should be deployed to. Here you can choose to leave it empty or using a specific smartlabel or whatever you need it for.
After that you have to add credentials of a user who has the right to add the targeted devices to the targeted AD securitygroups.
Pro Tipp: Only use Domain Administrator if you are in a lab :)  
sma_aag_002.png

We don't need a notification and the shedule is up to you. Maybe you wan't to run it every monday to be sure that every device is in the correct group(s). 
Necessary to check is the "Allow run without a logged-in user". 
sma_aag_003.png

And now the final step: Upload the VBS as dependency and configure a task (or multiple).
sma_aag_004.png

Of course you can do here whatever you want. Feel free to proof registry keys or whatever you like before adding a computer to an AD securitygroup. 
You can add all securitygroup names seperated by a space as an argument. So you are able to create different sets of joining ad groups in one task. 

You can download the script together with my AutoIt Wrapper for KACE SDA:  Here 

Please note that this is a selfmate script without vendor support.

Kind Regards
Timo
Be the first to comment

Basic Software Distribution Example

I've had a lot of positive feedback on my example of how I do a managed software distribution, so I thought I would share my instructions.  Feel free to contact me if you have any questions.


KACE Software Distribution

First Step is to creating a Software Distribution package is to gather up all the installation files required and zip them up into a since zip file.  Be careful the files are at the root of the zip and not in a folder at the root of the zip file (This could cause failures).

Save the zipped file to a location accessible when uploading to the KACE web interface.

Now, log into your KACE environment and pull up a current inventoried PC that already has that software installed.  Expand the Installed Programs field under Device Inventory.  Find the software and click on the hyperlink for it.  Please note that this must be the exact same version of the zipped package.

Under the Manage Operating Systems, ensure all OS versions you plan to distribute this to are selected (Note that with version 8 release of KACE, you can select entire OS Versions instead of individual versions as an option.)

Click on the Browse button, browse to and select the zipped file you have saved.

After selecting the file, change the Category and Threat Level as needed.  Click Save button when finished.

Navigate to Home>Label Management, then click Labels

Under Labels, click Choose Action and select New Manual Label.

Complete Name, Description and selections for Restrict Label Usage To.  Click Save when finished. Note: I start Software Installation Labels with SIL (Software Installation Label) for Best Practices

Navigate to Distribution>Managed Installations.  Under File, click New.

Configure Name, Execution; choose the software from the drop down options (Choose the one you uploaded earlier)

Note that with Version 8 you can choose Cataloged Software or Software from the Software list.  Your uploaded zip file will be associated under Software.


Now choose the installation commands.  Most often you will choose Override Default Installation to include switches such as silent installation.

Under Deploy, click Manage Associated Labels and select the label you created for this distribution and apply it.

Configure Notifications to give the user warnings and completion messages.

Configure Schedules as needed (What times it is permitted to install and how many attempts until it reports failed, etc.)  Click Save when complete.


Now, to have software install apply to devices, you will need to Apply the new Label to any device you wish to install it on.  After the device inventories next, it will install per configured settings.


NOTE: If device has a local KACE Repository, this may not work until the repository has obtained a local copy of this distrubtion (sometimes up to 24 hours)




http://www.itninja.com/refer/DaveMT




View comments (1)

ScriptLogic and Realtimepublishers Launch Windows Desktop Administration eBook

http://scriptlogic.com/eng/pressroom/PressReleases/PR-2003-01-28.asp

Definitive Guide is a Must Read for Every Network Administrator

Pompano Beach, FL – January 28, 2003 – ScriptLogic Corporation (www.scriptlogic.com), the leader in desktop administration software for Windows-based networks, and Realtimepublishers.com, Inc., the worldwide leader in corporate sponsored e-publishing, today announced the release of The Definitive Guide to Windows Desktop Administration. This new eBook, sponsored by ScriptLogic and authored by Bob Kelly, one of the industry’s top Windows management experts, provides valuable guidance and real-world examples for creating an efficient desktop administration plan.

“We are very excited to sponsor The Definitive Guide to Windows Desktop Administration,” said Jason Judge, CEO of ScriptLogic Corporation. “This eBook provides its readers with great, practical information about how to lower the total cost of ownership of their Windows-based networks-- something we know a lot about. The eBook complements our goal of helping customers reduce the time and money spent maintaining their networks.”

The Definitive Guide to Windows Desktop Administration examines the life cycle of Windows desktop administration from the initial OS deployment to change management through best practices. Topics included in this eBook will help readers learn how to do the following:

Reduce Help desk and administration costs and increase user productivity

Define and automate administration tasks using the latest tools and technologies

Manage security with Group Policy and desktop lockdown

Manage user profiles and map network resources

Embrace ‘best practices’ and script custom solutions

Exclusive to ScriptLogic, The Definitive Guide to Windows Desktop Administration will be published on a chapter-by-chapter basis, as it is written, providing an in-depth look at how to manage the Windows desktop. Registered readers will receive email notification when each chapter of the eBook is made available for download. Readers can register now for the eBook at www.scriptlogic.com/ebook.

“ScriptLogic is a well established leader in the Windows desktop administration arena and we are very excited to be partnering with them to make The Definitive Guide to Windows Desktop Administration available to our readers,” said Sean Daily, CEO of Realtimepublishers. “In these challenging economic times, it is even more important for enterprises to reduce TCO through efficient desktop administration and we know our readers will appreciate this free resource.”

The Definitive Guide Series

The Definitive Guide eBook series provides timely IT content written for technical professionals, including system administrators, senior IT personnel, advanced users, and consultants. The titles in this series provide a wealth of information that goes beyond whatÂ’s found in product manuals and white papers, and are written by expert authors who are veterans in their respective fields. The Definitive Guide series, like all RealtimepublishersÂ’ series, are high-quality eBooks that are free to readers on the Web sites of industry-leading, high-tech companies around the world.

About The Author

Bob Kelly is the founder of AppDeploy.com and author of an upcoming book about the KiXtart scripting language. Bob is recognized as an industry expert in the area of application and OS deployment—writing, speaking and consulting on these and other related topics. With 13 years of experience in engineering and support, he currently works as the principal consultant in the support of several enterprise networks providing scripting, repackaging, migration, and implementation services at Integrated Data Systems in Chantilly, VA

About ScriptLogic

ScriptLogic Corporation is the leader in desktop administration software for Microsoft Windows-based networks. ScriptLogic, its award-winning, patent-pending, flagship product is the first commercial software to combine logon scripting, group policies and user profile management – into an intuitive graphical management console supporting all 32-bit Windows platforms (95, 98, Me, NT, 2000 and XP). An innovative, multi-functional solution, ScriptLogic eliminates redundant tasks, repeated trips to each desktop, maintaining multiple batch files and many other time consuming, labor-intensive activities – leaving IT staff free to concentrate on more critical issues. With deployments ranging from 10 to over 40,000 seats, ScriptLogic offers significant benefits to any size network. ScriptLogic, a privately held company, is headquartered in Pompano Beach, Florida and can be reached at (954) 861-2300 and on the web at www.scriptlogic.com.

About Realtimepublishers.com

Realtimepublishers.com is the worldwide leader in corporate-sponsored e-publishing. The company is revolutionizing the publishing industry through its unique approach of creating high-quality titles and publishing them at no charge to readers on the Web sites of industry-leading companies around the world. Current Realtimepublishers eBook sponsors include Citrix Systems, Microsoft, NetIQ, New Moon Systems, Quest Software, Aelita, and more. For information about Realtimepublishers and available eBooks, please visit www.realtimepublishers.com.

Be the first to comment

Copying files from SMS Distribution points using command line

When using a command line with SMS (.cmd) it will default to using the current windows path.

Using this command will insert the current path which is hany when rolling out from multiple distribution points as it is updated depending on what server share its in.

For example you would use this line:

xcopy.exe "%~dp0*.*" c:\temp /E /I /Q /H /Y

The %~dp0 is replace with the current server path.

Be the first to comment

How TO: Track Windows and Office Product Keys

I’ve been getting a lot of request for this in my trainings, so here it is. 
At the end of this post, you will have all the tools you need to track your Windows product keys and Microsoft office product keys. 
They way this works is we find the keys using nirsoft's keyfinder program. 
Next a VBS writes the keys to the registry. 
Finally we tie it all together with custom inventory rules. 

Requirements:Product Finder (now form Nirsfot) 
Here is the link to the portable version
http://www.nirsoft.net/utils/produkey.zip 

First thing we need to do is copy this VBS code into notepad and save it as keys.vbs 

Option Explicit

Dim objFSO			
Dim objTextFile
Dim winKey 
Dim officeKey
Dim strFile
Dim arrKeys
Dim i

Const ForReading = 1
Const winCDLine = "Windows"
Const officeCDLine = "Microsoft Office"
Const noViso = "Visio"
Const officeKeyReg = "offKey"
Const winKeyReg = "winKey"


Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objTextFile = objFSO.OpenTextFile _
    ("keys.csv", ForReading)

'Read the file into the array
strFile = objTextFile.ReadAll
arrKeys = Split(strFile, vbCrLf)

For i = LBound(arrKeys) To UBound(arrKeys)
	'try to find the windows product key
	If(instr(arrkeys(i),winCDLine))Then
		winKey = getKey(arrKeys(i))
		writeReg winKey,winKeyReg	
	End If
	'try to find the office product key
	If(InStr(arrKeys(i),noViso)) Then
	
	ElseIf(InStr(arrKeys(i),officeCDLine)) Then
		officeKey = getKey(arrKeys(i))
		writeReg officeKey,officeKeyReg
	End If
Next

Function getKey(strKeyLine)
Dim temper
Const KeyLoc = 2
Const ProdLoc = 0

temper = Split(strkeyLine,",")
getKey = temper(prodloc) & "_" & temper(KeyLoc)

End function


Sub writeReg(strValue,StrValueName)

Dim strComputer
Dim oReg
Dim wshShell

Const HKEY_LOCAL_MACHINE = &H80000002
Const strKeyPath = "SOFTWARE\TVG"
Const strKeyPath64 = "SOFTWARE\Wow6432Node\TVG"
Const is64Key = "SOFTWARE\Wow6432Node"

strComputer = "."

Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _ 
    strComputer & "\root\default:StdRegProv")
Set WshShell = WScript.CreateObject("WScript.Shell")

'check for 64 bit
If(OS64()) Then
	oReg.CreateKey HKEY_LOCAL_MACHINE,strKeyPath64
	oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath64,strValueName,strValue
Else
	oReg.CreateKey HKEY_LOCAL_MACHINE,strKeyPath
	oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
End If

End Sub

Function OS64()
Dim objOS
Dim colItems
Dim objItem
Dim strComputer

strComputer = "."
Set objOS = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2")
Set colItems = objOS.ExecQuery("SELECT OSArchitecture FROM Win32_OperatingSystem")

'this should fail on 32 bit XP
On error resume next
For Each objItem In colItems
	If(IsNull(objItem.OSArchitecture)) Then 
		OS64 = False
	ElseIf(InStr(objItem.OSArchitecture,"64") > 0) Then
		OS64 = True
	Else 
		OS64 = False
	End If
Next
On Error Goto 0

If(Err <> 0) Then 
	OS64 = False
End if
End Function
 
Next thing we need to do is go to the scripting module and a new script. 
For script type select Online Shell Script. 
Choose a label, select windows as the operating system and set the script to run as local system. 
Next upload produkey.cfg, produkey.exe (both found in the nirsoft folder, make sure you unzip) and keys.vbs as dependencies. 
For the script text enter the following 2 lines. 
ProduKey.exe /windowskeys 1 /officekeys 1 /iekeys 0 /sqlkeys 0 /exchangekeys 0 /extractedition 1 /scomma keys.csv
cscript.exe keys.vbs


Last thing we need to do is change the script name from script.sh to script.bat (just below the script text). 

Now that we have the keys in the registry we can start creating the custom inventory rules. 
Go to the software module and add a new item. 
Call the first one “Windows Product Key” 
Select all your windows operating systems for supported OSs. 
Finally here is the syntax for the custom inventory rule: 
RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\TVG,winKey,TEXT)

Go ahead and save the software. 
Next add another item but this time call it "Microsoft Office Key" 
Highlight all the windows OSs again. 
Here is the syntax for the second piece of software. 
RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\TVG,offKey,TEXT)


At this point you could also create additional software records, for example one for each office key. 
That way depending on the key you would have a unique software title. This way you could use the KBOXs built in asset management module and do licence compliance. 

Below are two reports that you can use to see what machines have what keys installed. 
Office report: 
SELECT M.NAME,
       SUBSTRING_INDEX(MCI.STR_FIELD_VALUE,'_',1) AS OFFICE_VERSION,
       SUBSTRING_INDEX(MCI.STR_FIELD_VALUE,'_',-1) AS PRODUCT_KEY
FROM   SOFTWARE S,
       MACHINE_CUSTOM_INVENTORY MCI,
       MACHINE M
WHERE  MCI.SOFTWARE_ID = S.ID 
       AND M.ID = MCI.ID
       AND S.DISPLAY_NAME = 'Microsoft Office Key'
ORDER  BY OFFICE_VERSION,
          PRODUCT_KEY


Windows report: 
SELECT M.NAME,
       SUBSTRING_INDEX(MCI.STR_FIELD_VALUE,'_',1) AS WINDOWS_VERSION,
       SUBSTRING_INDEX(MCI.STR_FIELD_VALUE,'_',-1) AS PRODUCT_KEY
FROM   SOFTWARE S,
       MACHINE_CUSTOM_INVENTORY MCI,
       MACHINE M 
WHERE  MCI.SOFTWARE_ID = S.ID 
       AND M.ID = MCI.ID 
       AND S.DISPLAY_NAME = 'Windows Product Key'
ORDER  BY WINDOWS_VERSION,
          PRODUCT_KEY


I hope this is useful. 
Thanks to vacuna for helping me put this together. 
View comments (9)
Showing 1 - 5 of 348 results

Top Contributors

Talk About License Management