Silver Monkey v5 Documentation¶

Note

Documentation is still in development process. Please do not hesitate to contact us on support@silvermonkey.net for further information.

Welcome¶

This document is meant to be a source for all information regarding the administration and installation of Silver Monkey v5 Modules.

Contents:

Requirements¶

Server Application (IIS)¶

Microsoft Windows Server 2012 R2 or higher
Internet Information Server
Microsoft .NET Framework 3.5
Microsoft Report Viewer 2012 (free download from Microsoft)

Server Database (SQL)¶

Microsoft SQL Server 2014 or higher
Or Microsoft SQL Server Express with Advanced Services

2014: https://www.microsoft.com/en-US/download/details.aspx?id=42299

Server Hardware Requirements (IIS+SQL)¶

The system requirements for processors, RAM and hard disk space on the server depend on the size of the correspondig ConfigMgr environment and the number of users working at the same time. Anyway, there is always the option to easily move the application to a more powerful machine or to distribute it across several servers with load balancing.

System Requirements¶

2 CPU 1GHz
RAM 8GB (If there is a SQL Server running on the Webapplication Server 4GB RAM are required)
Database size 1000MB
Website/Application files 500MB

(Valid for up to 15,000 systems and 20 concurrent users on the Web Application)

Network Configuration¶

SIM v5 Engine supports multiple domain configurations. Please see figure below for detailed information about network communication ports:

Workplace Applications¶

Microsoft Internet Explorer 8 or later
Mozilla FireFox 5 or later (Windows SSO is not supported by browser)
Google Chrome

Installation¶

In this article:

Requirements
Report Builder
IIS Features
Microsoft SQL Server
Website Files
Database
IIS Configuration

Requirements ¶

For general information on system requirements see Requirements.

Report Builder ¶

In order to build reports on the website and to export lists in Microsoft Excel format the following libraries have to be installed:

Report Viewer 2010
Report Viewer 2012
- Which needs SQLSysClrTypes

Download library.

IIS Features ¶

Execute the following command to enable IIS features on the application server:

CMD.EXE /C DISM.EXE /enable-feature /all /online /featureName:IIS-WebServerRole /featureName:IIS-WebServer /featureName:IIS-CommonHttpFeatures /featureName:IIS-StaticContent /featureName:IIS-DefaultDocument /featureName:IIS-DirectoryBrowsing /featureName:IIS-HttpErrors /featureName:IIS-HttpRedirect /featureName:IIS-ApplicationDevelopment /featureName:IIS-ASPNET /featureName:IIS-NetFxExtensibility /featureName:IIS-ASPNET45 /featureName:IIS-NetFxExtensibility45 /featureName:IIS-ASP /featureName:IIS-CGI /featureName:IIS-ISAPIExtensions /featureName:IIS-ISAPIFilter /featureName:IIS-ServerSideIncludes /featureName:IIS-HealthAndDiagnostics /featureName:IIS-HttpLogging /featureName:IIS-LoggingLibraries /featureName:IIS-RequestMonitor /featureName:IIS-HttpTracing /featureName:IIS-CustomLogging /featureName:IIS-ODBCLogging /featureName:IIS-Security /featureName:IIS-BasicAuthentication /featureName:IIS-WindowsAuthentication /featureName:IIS-DigestAuthentication /featureName:IIS-ClientCertificateMappingAuthentication /featureName:IIS-IISCertificateMappingAuthentication /featureName:IIS-URLAuthorization /featureName:IIS-RequestFiltering /featureName:IIS-IPSecurity /featureName:IIS-Performance /featureName:IIS-HttpCompressionStatic /featureName:IIS-HttpCompressionDynamic /featureName:IIS-WebDAV /featureName:IIS-WebServerManagementTools /featureName:IIS-ManagementScriptingTools /featureName:IIS-ManagementService /featureName:IIS-IIS6ManagementCompatibility /featureName:IIS-Metabase /featureName:IIS-WMICompatibility /featureName:IIS-LegacyScripts /featureName:IIS-FTPServer /featureName:IIS-FTPSvc /featureName:IIS-FTPExtensibility /featureName:NetFx4Extended-ASPNET45 /featureName:IIS-ApplicationInit /featureName:IIS-WebSockets /featureName:IIS-CertProvider /featureName:IIS-ManagementConsole /featureName:IIS-LegacySnapIn /norestart

See Download Script.

Microsoft SQL Server ¶

For information about supported SQL Server versions see Supported Configurations.

The installation of the SQL Server will be described in the following section.

Installation Setup ¶

Start the SQL Server installation setup. Choose the option “New SQL Server stand-alone installation…” in the follwing Window:

Throughout the installation, please choose the same features as shown below:

Name the instance SIM or choose another name:

Configurate the server as follows:

Choose the Database Engine called ‘SQL_Latin_General_CP1_CI_AS’:

Select the ‘mixed mode’-authentification and add your SQL service account as SQL Server administrator:

You have completed the setup!

SQL Server TCP/IP Configuration ¶

Open the SQL Server Configuration Manager, choose ‘SQL Server Network Configuration’ and then ‘Protocols for [Database Name]’. Change the TCP/IP Status to Enabled:

Right-click the TCP/IP line and choose ‘Properties’:

Choose the tab “IP Adresses” and change the ‘TCP Port’-entry to 1433:

Afterwards, navigate to the SQL Server Services and restart the ‘SQL Server ([Database Name])’:

SIM SQL DB Service Account ¶

Visit KB00020 - SIM SQL Database Rights to see how to create the Silver Monkey service account necessary for the DB connection.

You have finished the basic SQL Server installation for Silver Monkey.

Website Files ¶

Copy the basic configuration of the website to the specified path on the web application server:

*C:\inetpub\wwwroot\[HERE]* Example: *C:\inetpub\wwwroot\SIM_R001*

This configuration will be customized later based on the customer requirements.

Tip

Make sure that the role “Everyone” has the permission to “Modify, Read& execute, List folder contents, Read, Write” to the App_Data folder (as seen below)

_images/SQL_server_Security_App_Data.png

Database ¶

Install the Silver Monkey Database Backup. The Backup is part of the installation Package.

See: KB00004 - Restoring SIM Database for more Information.

IIS Configuration ¶

Open the IIS (Internet Information Services) Manager. An app pool has to be created for the SIM Packaging website with the .NET CLR Version ‘v2.0.50727’ and the ‘Integrated’ Managed pipeline mode.

Navigate to the advanced settings of the created application pool (Figure 3) and set the ‘Idle Time-out(minutes)’ parameter to ‘600’. Set the ‘Idle Time-out Action’ parameter to ‘Suspend’.

Next, choose the ‘Add Application’ option in the right-click dialogue of the Default Web Site, choose the name of the application, the application pool that has just been created and the website folder that you copied in the C:inetpub\wwwroot… directory.

After this navigate to the ‘Authentication’ settings of the new application. Set the authentication as seen below:

For some features, it is necessary that a second AppPool is created using these settings:

Licence ¶

Your Licence is part of the license certificate. Your can find an Information on this topic here: KB00013 - Activating and Updating License Key

Setting up Database Connection ¶

Silver Monkey Administrator rights are required to set or update the SQL Server Connection via the user interface. If the “Settings”-Tab is visible, you got the required rights:

Fill in the fields in the Database Settings:

Click the ‘Save’-button, click the ‘Check database (save before)’-button.

The following Pop-Up shows the test result. If the test was not successfull, please check if the specified account has the correct user rights.

Setting up ConfigMgr Connection ¶

Silver Monkey Administrator rights are required to set or update the Configuration Manager Connection. If the “Settings”-Tab is visible, you got the required rights:

Expand the ‘Sites’ entry on the left side and choose ‘New site’:

Fill in the red-lined fields as seen below.

Visit: KB00017 - Configuration Manager Rights to see which rights are required for the SCCM Service account and the SCCM SQL Service account.

Click the ‘Create’-button.

Note

The rest of the fields will be filled in in the configuration step of the implementation.

Manual¶

Contents:

General Configuration¶

Warning

This article is under construction! Please DO NOT use any of the instructions below, yet! You may cause damage to your system. This article will be finished soon.

In this article:

Roles ¶

Create roles to limit the permissions of predefined users. You can either define a group as default group (every user gets this role), or define a specific link to an Active Directory group. You can set permissions to limit the users access on functions, reports, lists or modules.

Click the “+ New Role”-Button to create a new role:

Property	Description
Name	The general name of the role.
Description	The role description.
AD Group	Here you can define an LDAP Path to an AD Group. All Users of the AD Group will get the configured role.
E-Mail	Depricated.
Default Group	If you choose this option every user will get this role.
Show functions	Enables the user to see the functions tab in the main menue.
Show Shop	Enables the role to see the software shop.
Show CMDB	Enables the role to see the CMDB module.
Show packaging	Enables the role to see the packaging tab.
Show reports	Enables the role to see the reports module.
Show management	Enables the role to see the management module.
Edit settings	Enables the role to edit the settings of the SIM instance. Only an option for administrators.
Shop Administrator	Enables the role to edit requests in the software shop.
Proces admin	Enables the role to use the set status function.

Sites ¶

Create a new site via the “+ New site”-Button to connect the Packaging Module to your SCCM Site/SCCM database:

Common Settings ¶

Property	Description
Name - de	Displayed German name of the site.
Name - en	Displayed English name of the site.
Description - de	German site description.
Description - en	English site description.
Site code	The site code of your SCCM Site. (The site code has to be unique to one site).
SCCM Server	Hostname of the SCCM Server.
Domain	Domain of the SCCM service account.
Domain account	Name of the sccm service account. This account is used for all functions. (specify without domain) To see which permissions this accounts needs please see the reference at the end of this subsection.
Domain password	Password of the SCCM service account.
Impersonation	You have to choose this option if the installation is directly on the SCCM server.

Database settings ¶

Property	Description
Database server	Specify the SCCM SQL database server. (IP adress or FQDN)
Database name	Name of the SCCM SQL database.
Authentication	Choose the type of database authetication: SQL or Windows authentication. If you choose Windows authentication the domain account specified in the common settings will be used.
SQl user	Name of the SCCM SQL database service account (if you chose SQL authentication).
Name - en	Password of the SCCM SQL database service account (if you chose SQL authentication).

Function Settings ¶

Property	Description
Package displayname	Defines how SIM displays the package displayname in an SQL syntax. (e.g. Manufacturer+’‘+Name+’‘+Version+’‘+Language).
Package filter	Defines an SQL based fitler for the displaying of the packages in the Operations Module.
Computer filter	Defines an SQL based fitler for the displaying of the computers in the Operations Module.
User filter	Defindes an SQL based fitler for the displaying of the users in the Operations Module.
Application filter	Defines an SQL based filter for the displaying of the applications in the Operations Module.
Comp.software.query	SQl Query that is used to detemine the software that is installed on a computer.
Comp.app.query	SQl Query that is used to detemine the applications that are installed on a computer.
Coll. group tag	Documentation pending!
Depl. role tag	Documentation pending!
Package archive tag	Documentation pending!
Default program	Documentation pending!
Pkg.var. name	Documentation pending!
Pkg.var. value	Documentation pending!
Pkg.var. locale	Documentation pending!
App.var. name	Documentation pending!
App.var. value	Documentation pending!
App.var locale	Documentation pending!
No OS check on deployments	Documentation pending!
Software from variables in prozesses	Documentation pending!

Computer Software Deployment ¶

Property	Description
Parent folder	Folder that acts as a container for all dynamically generated Distribution-Collections (SCCM 2012 only) for computers.
Limited Collection	Collection that acts as a container for all dynamically generated Distribution-Collections (SCCM 2012 only) for computers.
Coll.name rule	Naming rule for the creation of new dynamically generated advertisements for computers. You can use the follwing fields as Placeholders : “{PackageName}”, “{ProgramName}”,”{AdvertisementType}”,”{OfferType }” and also all fields of the “SMSPackage”-table in the SCCM database. Example: “CMP PackageName ProgramName AdvertisementType OfferType”
Advert.name rule	Specify an optional folder for the creation of dynamically generated advertisements for computers.

User Software Deployment ¶

Property	Description
Parent folder	Folder that acts as a container for all dynamically generated Distribution-Collections (SCCM 2012 only) for users.
Limited Collection	Collection that acts as a container for all dynamically generated Distribution-Collections (SCCM 2012 only) for users.
Coll.name rule	Naming rule for the creation of new dynamically generated advertisements for users. You can use the follwing fields as Placeholders : “{PackageName}”, “{ProgramName}”,”{AdvertisementType}”,”{OfferType }” and also all fields of the “SMSPackage”-table in the SCCM database. Example: “CMP PackageName ProgramName AdvertisementType OfferType”
Advert.name rule	Specify an optional folder for the creation of dynamically generated advertisements for users.

E-Mails ¶

Configure mails for workflows or forms here.

Email-Group ¶

Property	Description
Name - de	German name for the email-group
Name - en	English name for the email-group

Email ¶

Condition ¶

Define a condition that decides wheather the email should be sent or not. If this is left empty, the email will always be sent. Concatenate rules by using “AND”. The following operators are avalible in the condition field:

Operator	Description
=	equals
<	less than
>	more than
!	does not equal
{roles} # Software Change Manager	“roles” contains the inserted Software Change Manager (case sensitive)
{roles} ^ Treon User	“roles” does NOT contain the inserted Treon User (case sensitive)

Note

The last two operators are role filters and will ONLY be working on {roles}!

Furthermore, you can use palceholders that reference to attributes of the associated workflow as seen in the following example:

1	{Manufacturer}=Adobe AND {Product}!Reader

In this case, the email will be sent if the Workflow parameter “Manufacturer” is filled with the value “Adobe” and the parameter “Product” does not equal “Reader”.

Recipient ¶

Defines the recipient of the email. You can specify a concrete adresse such as “support@silvermonkey.net” or use different placeholders:

Property	Description
{TicketResponsible}	Takes the value of the specified attribute in the workflow context.
{$MAIL>IssueEditor}	Takes the email adress of the specified Active Directory field in the workflow context.
{@OBJ.PartnerResponsiblePerson.Email}	Takes an entry out of another table/class that is connected to the main class and Workflow context. Syntax: {@OBJ.Table.Column}

Example:

1	{@OBJ.PartnerResponsiblePerson.Email}

Seperate multiple recipients with a semicolon.

Subject ¶

The subject in the email. You can use the same placeholders as you do in the recipient.

Example:

Your request was cancelled {RequestManufacturerName}_{RequestProductName}_{RequestProductVersion}_{@OBJ.PackageLanguage.CodeISO6391}_{Architecture}_{@OBJ.PackageType.Character}{PackageID}

Message ¶

The message of the email. You can use the same placeholders as you do in the recipient.

Example:

<font face="Arial" size="2">
The software package: {RequestManufacturerName}_{RequestProductName}_{RequestProductVersion}_{@OBJ.PackageLanguage.CodeISO6391}_{Architecture}_{@OBJ.PackageType.Character}{PackageID} was canceled.
<br>
<br>
<br>Rejection Reason: {Rejectionreason}
<br>
<br> If you are missing any information please look up the history of the request or get in
<br> contact with the Software Change Manager.
<br>
<br> For more details about the package see packaging factory:  click <a href="{@OBJ.PackagingClient.TreonURL}/Support/TypeView.aspx?PopUp=true&TypeViewId=46&Id={Id}">this link</a>
</font>

Workflows ¶

Configure workflows for the CMDB and the packaging process.

Property	Description
Name - de	German name of the workflow.
Name - en	English name of the workflow.

Status ¶

Note

Change the position of a status with the green arrows in the status definition.

Property	Description
Name - de	German name of the Status.
Name - en	English name of the Status.
Token	Define the roles that have the permission to edit Forms in this Status. You can define multiple roles seperated with a semicolon.
Plausibility	Define a condition that decides wheather or not the buttons to proceed to this status will be displayed. See the Condition Section in the previous chapter for more details.
Only visible when status is active	Enable this option to hide the status in the form until the form has reached this status. (Usefull for rejected status)

Follower ¶

Property	Description
Follower	Choose another workflow status as follower.
Function text - de	German label text of the button to change the status to the one specified in the follower field. If you enter nothing the label of the targetet workflow status will be displayed.
Function text - en	English Label Text of the button to change the status to the one specified in the follower field. If you enter nothing the label of the targetet workflow status will be displayed.
Message - de	Define the german text of the message box that will be displayed when the status is changed to the follower.
Message - en	Define the english text of the message box that will be displayed when the status is changed to the follower.
E-mail group	Choose an email group that will be triggerd when the status is changed to the follower. This has the advantage that conditions from the email group are enabled (See the previos chapter for details regarding emails).
E-Mail recipient	Manually choose an email recipient. (See the previos chapter for details).
E-Mail subject	Manually choose an email subject. (See the previos chapter for details).
E-Mail message	Manually choose an email message. (See the previos chapter for details).
Reject	Choosing this option changes the appearance of the follower-button and creates a popup that will appear when the button is clicked.

Interfaces ¶

The interfaces provide a simple and efficient way to fill or to equalize the SIM database with data from SCCM or other databases. This is done best by using the SQL Merge command. Unless the databases are not on the same Microsoft SQL Server, the source server has to be made familiar to the SIM database server via a linkserver:

Example of the adjustment of computer objects from SCCM into SIM database. New computers are automatically created, existing ones are updated and obsolete ones are deleted in SIM:

MERGE treonV5.dbo.Computer AS t
USING (
      SELECT ResourceID, Name0
      FROM   [SCCM_Servername].SMS_P01.dbo.v_R_System
      WHERE  ISNULL(Obsolete0,0) = 0
) AS s
ON s.ResourceId = t.ItemKey

WHEN MATCHED THEN
      UPDATE SET t.ItemKey = s.ResourceId,
                 t.Name = s.Name0,
                 t.SysDisplayName = s.Name0

WHEN NOT MATCHED THEN
      INSERT ( ItemKey,
               Name,
               SysDisplayName )
      VALUES ( s.ResourceId,
               s.Name0,
               s.Name0 )

WHEN NOT MATCHED BY SOURCE THEN
        DELETE;

Example of the adjustment of software objects from SCCM into SIM database. New packages are automatically created, existing ones are updated and obsolete ones are deleted in SIM:

MERGE treonV5.dbo.Software AS t
USING (
      SELECT PkgId, Name, Version, Language, Manufacturer
      FROM   [SCCM_Servername].SMS_P01.dbo.SMSPackages
      WHERE  PackageType=0
) AS s
ON s.PkgId = t.PkgId COLLATE Latin1_General_CI_AS

WHEN MATCHED THEN
      UPDATE SET t.Manufacturer = s.Manufacturer,
                 t.Product = s.Name,
                 t.Version = s.Version,
                 t.Language = s.Language,
                 t.PkgId = s.PkgId,
                 t.SysDisplayName = s.Manufacturer + ' ' + s.Name + ' ' + s.Version

WHEN NOT MATCHED THEN
      INSERT ( Manufacturer,
               Product,
               Version,
               Language,
               PkgId,
               SysDisplayName )
      VALUES ( s.Manufacturer,
               s.Name,
               s.Version,
               s.Language,
               s.PkgId,
               s.Manufacturer + ' ' + s.Name + ' ' + s.Version )

WHEN NOT MATCHED BY SOURCE THEN
        DELETE;

The interfaces are accessed via the CMDB function menu or called directly via the page “Support / ExecuteInterface.aspx”. A specified interface can be started right away, with the URL parameter “Interface”. Several interfaces can be successively launched by lining up several interface names seperated with semicolons. This process is suitable to be called in a Windows scheduled task.

Using Placeholders ¶

Placerholders are used to reference attributes in the life time execution of events (Sending emails, displaying formulars, querying databases etc.) Placeholders in XML definitions are useful in several scenarios. You can use them in the email definitions, form and list definitions and functions that use SLQ queries.

There are three main types of references:

Reference Type	Description	Example
{[AttributeName]}	References an Attribute in the current execution context.	{Name}
{$[ADParameter]>[AttributeName]}	Takes the desired part of the Active Directory Attribute that is referenced. You can use the follwing AD Parameters: [$MAIL] gives the email, [$NAME] gives the displayname,[$USERNAME] gives the username, [$ESCAPEDUSERNAME] gives the Domain + Username .	{$MAIL>Packageresponsible}
{@OBJ.[Table].[AttributeName]}	Takes an entry out of another table/class that is connected to the main class in the execution context. Syntax: {@OBJ.Table.Column}	{@OBJ.Issue.TicketResponsible}
{CURRENTUSER}	Shows the currently logged-on user.	{CURRENTUSER}

CMDB Class automation ¶

Within every CMDB Class (including “Packaging”) the automation attribute can be used to define two different types of automatic script triggering:

Executing an MSSQL Query in context of the SilverMonkey Database (default)
Executing an external process (like powershell) to run custom scripts

<trigger>

	<afterUpdate field="" value="" 
		command=" exec sp_MyMSSQLStoredProcedure @Id='{Id}' " 
	/>

	<afterUpdate field="" value="" title="executeMyScript"
		script="C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe"
		arguments="C:\SilverMonkey\v5\Tools\MyScript.ps1 -ID {Id}" 
		condition="{SysStatus} = A1 - Request" 
		restart="false" 
		back="true" 
	/>

</trigger>

The corresponding setting can be found here:

Form Definition ¶

Form Elements ¶

Form elements are displayed in detail forms.

Every form element has to be definded in the XML block <views><view><controls>.

Note

In the following sections, you will finde code-blocks filled with example code. Expressions in square brackets in the tables below are placeholders. Please be sure to replace the example code with specific expressions for your case if you want to copy and use xml statements from this page. (e.g. if you want to display a widget 300 pixels wide, change width=”250” to width=”300” **or* replace width=”[width in px]” with width=”300” ).

Headline ¶

Enter the following code to display a headline:

1
2
3
4
<views>
<view>
<controls>
<headline text="ExampleClass" />
This is how a headline is displayed in the CMBD form.

Section ¶

Define a section as follows:

1
2
3
4
<views>
<view>
<controls>
<section text="ExampleSection" />
This is how a section is displayed in the CMBD form.

Paragraph ¶

Define a paragraph as follows:

<views>
<view>
<controls>
<paragraph text="This example paragraph has been created in order to test funtionality." />

Manual/General Configuration/_static/Paragraph.PNG

This is how a paragraph is displayed in the CMBD form.

Attribute ¶

Note

In order to use attributes as form elements, they will have to be created first. For full reference see Attributes.

You can add an attribute this way:

<views>
<view>
<controls>
<attribute
    field="attribute name"
    validation="*"
    readonly="false"
    width="250"
    height="50"
    setDefaultOnLoad="Name1"
    forceDefault="false"
    Comment="This is a comment."
/>

Manual/General Configuration/_static/Attribute.PNG

This is how attributes are displayed in the CMBD form.

Property	Description
field=”[string]”	The name of the attribute according to the object definition. Optional fields can also be used. They should have a constant name.
validation=”*”	Set up a validation rule (e.g. “” is used to ask for obligatory input). Example: validation="" validation="required: true, regexp: /^[A-Za-z\d]+$/i" validation="required: true, regexp: /^[A-Za-z\d]{2,20}$/i" Also available for Action buttons. The following resource keys (resource.xml) for Warning Messages Customization are given: uncompleted[Action Button] (i.e. uncompletedCopyFiles, uncompletedCMDB2SCCM, uncompletedExecute, uncompletedCreateActiveDirectory and so on).
readonly=”[true\|false]”	Distinguishes between reading mode and writing mode. Type in “true” for reading mode or “false” if you want to enable the user to enter text.
width=”[width in px]”	Width of the widget given in pixels.
height=”[height in px]”	Height of the widget given in pixels.
setDefaultOnLoad=”[true\|false]”	Defines the default value for an empty attribute that is set when the form is loading.
forceDefault=”[true\|false]”	Forces implementation of the default values.
Comment=”[strings]”	Add a comment to the attribute. It will be displayed when the curser is moved to the “*” at the end of the attribute.

Comment ¶

You can add comments to an object in the XML file that will not be displayed when it is executed.

<views>
<view>
<controls>
<comment text="[Example Comment.]" />

Connections ¶

These are connections to objects. It is possible to set up new connections or new objects. Add connections using the following xml statement:

<views>
<view>
<controls>
<connections
  width="385"
  height="200"
  id="connection1"
  title="ConnectionServer"
  filter="Software"
  link="true"
  create="view1; view2"
  readOnly="true"
  required="true/false"
/>

Property	Description
width=”[width in px]”	Displayed width in pixels.
height=”[height in px]”	Displayed height in pixels.
id=”[string/integer]”	Unique label if multiple connection lists are displayed.
title=”[string]”	Individual title for the connection list.
filter=”[type]”	Restricts the connection list to one single object type.
link=”[true\|false]”	Enables opening referenced objects.
create=”[viewX]”	List of object views which is supposed to be displayed when new objects are being set up and assigned.
readOnly=”[true\|false]”	Prevents user from setting up new connecitons if set to “true”.

Manual/General Configuration/_static/Connection.PNG

This is how a connection is displayed in the CMBD form.

List ¶

Display entrys of another class (e.g. table). It is possible to use placeholders for attributes in this statement.

Example:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
 <list
 id="Resources1"
 width="1200"
 title="Computer Titel"
 fields="Name,200~MACAdress,100~Language,898"
 count="SELECT count([id])
 FROM Computers"
 data="
 WITH myBase AS (
 SELECT [Id] ,
 [Name] ,
 [MACAddress] ,
 [Language] ,
 ROW_NUMBER() OVER (
 ORDER BY {order1}) AS POS
 FROM Computers



 )

 SELECT Id, Name, MACAddress, Language
 FROM myBase
 WHERE POS BETWEEN {start} AND {end}
 ORDER BY {order2} DESC

 "
 order1="Name~MACAddress~Language"
 order2="Name~MACAddress~Language"
 view="Computers Details"
 cmd="javascript: try {window.parent.gridTable.clearSelection();} catch (e){} try {window.opener.gridTable.clearSelection();} catch (e){} document.location.href='TypeView.aspx?PopUp=true&amp;TypeViewId={view}&amp;Id='+id"
 />
Property Description

id=”[string/integer]” Unique label if multiple lists are used in a single formular definition.

width=”[width in px]” Overall width of the list in pixels.

title=”[string]” Individual title for the list.

fields=”[SQLColumn~ColumnWidth,SQLColumn2~ColumnWidth2…] Used to determine the width of the columns in the list.

count=”[SQLStatementwithCountresult]” Used to display the number of entrys in the list.

data=”[SQLStatement]” The actual query that gets the data for the list.

order1=”[SQLColumn~SQLColumn2…]” Used to determine the order in wich the sql result will be displayed.

order2=”[SQLColumn2~SQLColumn…]” Alternative to order 1 that is also use to to determine the order in wich the sql result will be displayed.

view=”[ViewOfthereferencedClass]” Enables the option to open entrys of other classes via click on the list element. This defines the View that is used to display the data.

cmd=”javascript: try {window.parent.gridTable.clearSelection();} catch (e){} try {window.opener.gridTable.clearSelection();} catch (e){} document.location.href=’TypeView.aspx?PopUp=true&TypeViewId={view}&Id=’+id” Used for the opening of other classes.

Action Buttons ¶

Action buttons are buttons in detail forms. When a user has writing permission for the specific step he / she can click on that button. Action buttons are displayed on the right side of every detail form as the following image shows:

Every action button has to be definded within a view in the XML block <views><view><controls>. Please see the following example:

Execute ¶

Execution of a commandline or a script. The process will be executed in the context of the IIS application pool. However, you can use in the script impersonation for using specific accounts.

 <execute
    title="Title of the button"
    command="C:\windows\system32\cmd.exe"
    arguments="{Var1} {Var2} {Var3}"
    exit_1="Execution was sucessfully processed."
    exit_2="Error while execution. See log for details."
    exit_dynamic="true"
    wait="true"
    validation="*"
 />

Available attributes

Attribute	Description
title=”[Resource]”	Title of the button
command=”[PathToExe]”	Full path to the executable file. Environment variables are not supported.
arguments=”[{Var1} {Var2} {Var3}]”	Arguments passed to the executed process.
exit_nn=”[Resource]”	After execution the exit code will be passed to the website. If a corresponding exit_nn parameter is set, a pop up is displayed to the user.
wait=”[true\|false]”	If set to true, the website waits for the execution to end.
validation=”*”	Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

Warning

If “wait” is set to “true” be aware that the internet browser and the IIS session itself both have an IDLE timeout. Only use wait=”true” if the script is executed within seconds.

Examples:

Executing a batch file

 <execute
    title="My CMD Script"
    command="C:\windows\system32\cmd.exe"
    arguments="/C C:\SilverMonkey\Scripts\MyFirstscript.cmd {ID}"
    wait="false"
 />

Note

You can also execute scripts from a network path. Make sure that the IIS Application Pool is configured to use a specific service account (default is LOCALSYSTEM).

 <execute
    title="My CMD Script"
    command="C:\windows\system32\cmd.exe"
    arguments="/C \\networkpath\share\scripts\myscript.cmd {ID}"
    wait="false"
 />

Executing a powershell PS1 script

 <execute
    title="My PS1 Script"
    command="C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe"
    arguments="C:\SilverMonkey\Scripts\MyFirstscript.ps1 -PackagingJobId {ID} -OtherParam &quot;{Var1}&quot;"
    wait="false"
 />

Executing a powershell PS1 script with dynamic output

 <execute
    title="My PS1 Script"
    command="C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe"
    arguments="{APPPATH}\Tools\TestScript.ps1 -PackagingJobId {ID} -OtherParam &quot;{Var1}&quot;"
    wait="true"
    exit_dynamic="true"

 />

Checklist: My execute is not running my Power Shell script.

Did you set the executionpolicy on the system that is running the PS Script? (32/64 bit? use “get-executionpolicy -list” to display the present configuration)
Is the Identity that is defined in the IIS AppPool able to execute the specified script? (Check in the Identity property of the AppPool of your app)
Is the needed Power Shell version availible on your AppServer? ( Run $PSVersionTable.PsVersion in PoweShell and check)
Did you get the PS Script from the online share? Check if the script and its dependency’s are ‘unblocked’.(They will get a flag when they are downloaded that prevents them from beeing executed)
Double Check your XML in the form xml
Try to use dynamic output (See above example 3.) to get error output displayed in frontend

Tip

Using quations within XML attributes: "{Var1}" (HTML notation).

ExecutePS ¶

Warning

This function is deprecated because it only supports powershell up to version 2.0 and does not support cmdlets.

 <executePS
    title="My PS1 Script"
    command="C:\SilverMonkey\Scripts\MyFirstscript.ps1"
    arguments="[-PackagingJobId {ID} -OtherParam &quot;{Var1}&quot;]"
    wait="false"
 />

Note

The “return” command gives back a value from the PowerShell script to the form. In the example, the value “PSVarialbe $ComputerSID” is given back to the field “ComputerSID” in the current class. return "ComputerSID = “+"'"+$ComputerSID+"'"

Attribute	Description
title=”[string]”	Text in the head of the function.
command=”[command line]”	Command line (solved against the corresponding data record.
arguments=”[string]”	Arguments that call the command (solved against the corresponding data record). If arguments are supposed to be given to the PS script, put a hyphen before the value that you want to forward.
wait=”[true\|false]”	Waits for the execution to stop (in case of synchronous execution). Only if this value is set to “true” the system can send a report to the user.
validation=”*”	Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

CMDB2SCCM ¶

Creates or edits one or more computer objects in Microsoft ConfigMgr and performs additional actions regarding the systems:

Adding variables

Creating direct memberships for ConfigMgr Collections

The underlying code can be used in two methods:

Via mass import button in lists

Via action button in forms

Note

This action button was orignally used to fully import systems (mass import). By defining the CMDB mass import configuration to accept single systems by parameter also single systems can be imported.

See Setting up Mass Import for ConfigMgr for tutorial.
See CMDB-SCCM-transfer_. for more information.

<CMDB2SCCM
    title="Title of button"
    param="String"
    restart="true"
 />

Available Attributes

Attribute	Description
title=”[resource]”	Title of the button
param=”[string]”	String to pass to the SQL scripts executed on runtime of the mass import.
restart=”[true\|false]”	If set to false, the button will be invisible when executed once.
validation=”*”	Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

Example:

Executing a batch file

<CMDB2SCCM
  title="Transfer Computer to SCCM"
  param="SingleTransfer"
  restart="true"
/>

CopyFiles ¶

Opens a dialogue in which new directory structures can be set for the packaging workflow. (Copy is carried out in context of the background SCCM account.)

<views>
<view>
<controls>
<copyFiles
  restart="true"
  site="Packaging site name"
  indexFilter="true"
  indexFilterPreselected="false"
  title="Title"
  validation="*"
/>

CreatePackage ¶

Opens a dialogue in which you can compile the SCCM package for the packaging workflow.

1
2
3
4
5
6
7
8
<views>
<view>
<controls>
<createPackage
  restart="true|false"
  site="Packaging site name"
  sendToDP="true|false"
/>
Attribute Description

restart=”[true/false]” Enables repetition of the proces after the package has been created (e.g. in order to recreate the package after manual deletion).

site=”[Packaging site Name]” Defines on which packaging site the operation is to be carried out. If this attribute is not set, a parameter type “Packetierungssite” has to contain the information needed.

sendToDP=”[true|false]” Enables transmission to Distribution Points (“DP”).

validation=”*” Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

CreateCollection ¶

Opens a dialogue to create a new collection for the packaging workflow.

<views>
<view>
<controls>
<createCollection
  title="Ressource"
  folder="OrderId"
  parentCollection="CollectionId"
  name="Namensregel"
  collectionType="Typ"
  limitToCollectionId="CollectionId"
  query="Regelabfrage"
/>

Attribute	Description
title=”[string]”	Text of the header of the function.
folder=”[string / integer]”	Optional declaration of hte folder in which the collection is supposed to be compiled (from SCCM 2012). Note the ID of the folder - its name will not be deleted. A whole folder tree can optionally be set here. In this case, enter the ID of the folder an all folder names that should be set and connect them with a tilde. Example: 16777222~{Manufacturer}~{Product}~Install
parentCollection=”[string / interger]”	Optionally declare the collection in which the new collection is supposed to be saved (SCCM 2007).
name=”[string]”	Set a naming convention or the new collection.
collectionType=”[integer]”	Collection-type key (1: user, 2: computer).
limitToCollectionId=”[string]”	Limited collection for SCCM 2012.
query=”[string]”	Query for dynamic collections.
validation=”*”	Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

CreateApplication ¶

Opens a dialogue in which you can set up the SCCM Application for the packaging workflow.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
<views>
<view>
<controls>
<createApplication
  restart="true|false"
  title="Resource"
  titleRestart="Resource"
  site="Packaging site name"
  configuration="Name"
/>
Attribute Description

restart=”[true|false]” Enables repetition of the proces after the package has been created (e.g. in order to recreate the package after manual deletion.

title=”[string]” Name of the resource of the action button for initial creation of the application. (The corresponding text resource has to be defined in Ressources.xml.)

titleRestart=”[string]” Name of the resource of the action button for recreation of the application.

site=”[string]” Defines the packaging site where the operation has to be carried out. If this attribute is not set, the packaging job has to contain a parameter type “packaging site” in order to recieve the needed information.

configuration=”[string]” Name of the configuration for the application from the site settings.

validation=”*” Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

Comment ¶

Shows the possibility to enter a comment. All comments will be historicized.

<views>
<view>
<controls>
<comment="This comment and will be historicized." />

Save ¶

In order to display a save-button, enter the following XML code:

<views>
<view>
<controls>
<save
  delete="true|false"
/>

Attribute	Description
delete=”[true\|false]”	Add a delete-button.
validation=”*”	Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

SendMail ¶

Use the following XML statements in order to show a function to send preformatted Emails.

<views>
<view>
<controls>
<sendMail
  title="Welcome to SIM"
  from="support@silvermonkey.net"
  to="exampleclient@example.com"
  subject="Text"
  body="Lorem ipsum dolor."
  mailGroup="AllClients"
/>

Attribute	Description
title=”[string]”	Optionally declare a title to the button.
from=”[mail address]”	Sender’s mail address.
to=”[mail address]”	Recipient’s mail address(es).
subject=”[string]”	Subject of the email.
body=”[string]”	Body of the email.
mailGroup=”[string]”	Instead of adding the attributes “to”, “subject” and “body” you can refer to a predefined group. This simplifies simultaneously sending multiple mails.
validation=”*”	Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

ImportXML ¶

CreateActiveDirectory ¶

Creates an active directory object. The active directory will be authenticated with the Windows login data for your treon database. This is also the case if database authentication is set to “SQL”.

<views>
<view>
<controls>
<createActiveDirectory
  title="Active D"
  parentLDAP="Ldap path"
  class="SchemaClassName"
  name="naming convention"
  attribute="value"
/>

Note

You will have to outcode special characters when declaring the parentLDAP. This means a backslash will have to be put in front of commas, backslashes, the rhombus sign, the plus sign, angle brackets, semicolons, quotation marks and the equal sign.

Attribute	Description
title=”[string]”	Title of the action button.
parentLDAP=”[LDAP path]”	LDAP path of the container in which the object is supposed to be created.
class=”[string]”	Schema class of the object that is created.
name=”[string]”	Naming convention for the new object.
attribute=”[value]”	All further attributes are interpreted as object attributes and connected to the first object.
validation=”*”	Validation rule. If the validation rule is activated, you have to execute this Operation in order to proceed to the next workflow step.

List Definition ¶

You can create custom lists and customize them to fit your needs. The following subchapters describe the options you have when you are creating or customizing a list.

Properties ¶

Property	Description
Design	Choose initially between list and form.
Name - de / Name - en	The displayed name of the list
Sort order	Choose where to display the chosen list in the dropdown menu.
Roles	Choose wich roles can see the list.
Definition	The definition of the list.

Example List:

<view splitterWidth="550"
         detailView="Paketdetails PackWF"
         newLink=""
         viewPane="false"
         refresh="true"
         excelExport="true"
         importExport="false"
         popUp="1100,800">

<columns>
     <column field="ClientCode"  width="70" />
     <column field="RequestID"  width="70" />
     <column field="RequestReference"  width="70" />
     <column field="SysStatus"  width="180" />
     <column field="RequestManufacturerName"  width="200" />
     <column field="RequestProductName"  width="200" />
     <column field="RequestProductVersion"  width="100" />
     <column field="PackagingPackageName"  width="-1" />
     <column field="PackageSWGroups"  width="200" />
</columns>

<data>
     <condition> ({search}='' OR PackageProductName like {search} OR ClientCode like {search} OR RequestReference like {search} OR RequestID like {search}) </condition>
</data>
</view>

<view> Definition ¶

Parameters

View Options	Description
splitterWidth	Width of the splitter shown in list form. (in pixels)
detailView- de / Name - en	Specifies the form name that is to be used for the detailed representation of a list form.
newLink	Construction of new objects in a list. The “detailed view“ is used as detail form.
viewPane	If this value is set to “false“, the selection is displayed as a drop-down list.
refresh	Displays the update function in the list view.
excelExport	Displays the excel export function in the list view.
importExport	Displays the import/export function in the list view.
popUp	By specifying a pop-up window size in the format “width, height“ (in px), a list view opens choosen entries in a new window e.g .: “800,600“

<columns> Definition ¶

Columns represent Attributes and are used to display their values in a list. You can see the syntax in the following code-block.

Column Options	Description
Column field	The fieldname of the attribute to be displayed.
width	Width of the column in px.

<data> Definition ¶

In the <data> section you can define the initial search condition for the displayed list objects. You can also define in which attributes to search.

The highlighted part in the following code block causes the website to display just the entries that posses a value like ‘john doe’ in the attributes IssueEditor, Requestor or qualityinspector.

<condition>
   ({search}='' OR IssueID like {search} OR Title like {search})
AND
   (IssueEditor like '%John Doe%' OR Requestor like '%John Doe%' OR qualityinspector like '%John Doe%')
</condition>

The next highlighted part in the code block defines that the list search associated with that list will search in the attributes IssueID or Title.

<condition>
   ({search}='' OR IssueID like {search} OR Title like {search})
AND
   (IssueEditor like '%John Doe%' OR Requestor like '%John Doe%' OR qualityinspector like '%John Doe%')
</condition>

You can define very specific filters and conditions with TSQL in lists.

Attributes ¶

Different Types of Attributes

You can create different types of attributes to customize the form to your needs. These attributes have different settings and functions which are described in the two tables below.

Attribute Type	Description	Additional Options
String	Field that holds a text.	Default Value, Input mask
Date	Field that holds a date.	Default Value, Number Format
Integer	Field that holds an integer.	Default Value, Number Format
Big integer	Field that holds a big integer.	Default Value, Number Format
Float	Field that holds a float.	Default Value, Number Format
Multilanguage Text	– Deprecated –	– Deprecated –
Checkbox	Field that displays a checkbox, can have the Status ‘checked’ or ‘unchecked’.	Default value, Input mask
Data list	Field that holds a fixed list of entrys that can be defined in the GUI, the entrys are seperated with a semicolon (‘firstentry;secondentry’).	Items, Default Value, Fill stage
Config. list	– Deprecated –	– Deprecated –
SQL list	– Deprecated –	– Deprecated –
File	Contains files that are stored in the SQL Database.	Default value, Input mask
Object reference	Field that references to another table and displays the entrys defined in it.	Object reference, Filter, Default value
Active Directory User	Field that prevents users from being registered in the Active Directory Cache (the cashe is located in the SIM DB).	LDAP path, Default value
Active Directory Group	Field that prevents groups from being registered in the Active Directory Cashe (the cashe is located in the SIM DB).	LDAP path, Default
Packaging package name	– Deprecated –	– Deprecated –
Packaging operation system	– Deprecated –	– Deprecated –
Packaging site	– Deprecated –	– Deprecated –

Extended Attribute Functions/Options

Function	Description
Name - de / Name - en	The Displayname of the attribute.
Field name	This is the actual column name in the SIM SQL DB.
Database Type	Describes the attributes type.
LDAP path	LADP path for the AD Users/Groups.
Auto Postback	– Feature not used –
Suggestion	Autocomplete. If suggestions are enabled, recent entrys will be suggested.
Default value	Defines a default value that will be set automatically.
Logical Key	– Feature not used –
Input mask	Specifies the required format of the entry. Example: ----- (for MAC-Adresses) ‘*’ is a placeholder. A valid entry would be 11-11-11-11-11-11.
Number format	Defines the required format of every entry. Example: „#,##0.0“ „DD.MM.YYYY“
Items	Items of a data list seperated by semicolons. Example: Yes;No;(choose)
Fill stage	– Feature not used –
Object reference	Used for Object reference attributes. Choose the table you want to refer to.
Filter	Used for object reference attributes. Filter the entrys in the table you are referring to.
LDAP path	LADP path for the AD Users/Groups.

Manual for Module “CMDB”¶

Warning

This article is under construction! Please DO NOT refer to any of the instructions below, yet! You may cause damage to your system! This article will be finished soon.

In this article:

SCCM Transfer
- Single Computer Transfer Example
- Multiple Computer Transfer Example

SCCM Transfer ¶

The SCCM transfer module is basically a collection of SQL queries which are executed and delivered to SCCM. This way, customers can fully change the behaviour to their needs. In general SCCM transfer can be configured in two different modes:

Single computer transfer (used by form action button)
Multiple computer transfer (used by list action button)

You will find the configuration for SCCM trensfer in “Settings->CMDB”.

Function	Description
Description (de/en)	Info text displayed in the pop-up.
List query	Query which builds up the dropdown list in the pop-up.
Computer query	Selects mandatory data for computer import. It is important to stick to the correct order of the selected attributes: = Unique ID of computer element in SIM database = Target computer name = MAC Address = SMBIOS GUID (if available the computer will be created with SMBIOSGUID rather that MAC Address) Available variables: “{0}” = Selected (computer) item database IDs in the popup. “{roles}” = Roles the user is currently in. “{user}” = Username of the user currently logged in (DOMAINUsername). “{id}” = ID of the CMDB item. Note: Only available when opened via action button. “{param}” = Additional parameters defined in the view. Note: Only available when opened via action button.
Variable query	Variables added to the created SCCM computer object. It is important to stick to the correct order of the selected attributes: = Name of the computervariable = Value of the computervariable = Locale of the computervariable (if unknown please use ‘1031’) Available variables: “{0}” = SIM DB ID of the transferred computer object. “{param}” = Parameter string given by the corresponding action button parameter. Special variable prefixes: “ConfigMgrColl” = If the variable has this prefix, a direct membership will be created for the collection name. “ConfigMgrPrimaryUser” = If the variable has this prefix, a primary user relationship will be created (`DOMAIN\Username` notation).
Software query	Variable SCCM package list created at runtime and added as variables to the computer object.
Application query	Variable SCCM application list created at runtime and added as variables to the computer object.
Computer update	SQL script which is executed for every transfered computer with import result. Available variables: “{0}” = SIM DB ID of the transfered computer object. “{1}” = Message of the result. If successful the message is empty.
Site	Target SCCM site object (Settings->Sites).
Configuration	Computer configuration (variables, collections) which is the base for the creation of a new computer object.

Single Computer Transfer Example ¶

Exchange the following XML with the corresponding elements in your configuration.xml:

<cmdb2sccm_compConfiguration>MassImportDummy</cmdb2sccm_compConfiguration>
<cmdb2sccm_compFilterName lang="de">Bitte wählen Sie eine Rollout Einheit zum Transfer nach SCCM</cmdb2sccm_compFilterName>
<cmdb2sccm_compFilterName lang="en">Please select rollout unit für transfer to sccm</cmdb2sccm_compFilterName>
<cmdb2sccm_compFilterList>SELECT 0 as Id, 'Single Computer Import' as SysDisplayName</cmdb2sccm_compFilterList>
<cmdb2sccm_compQuery>SELECT Id, SysDisplayName, MACAddress FROM Computers Where Id = {id}</cmdb2sccm_compQuery>
<cmdb2sccm_softQuery>Declare @ComputerId as bigint
set @ComputerId =  {0}

select distinct t.PkgId from (

select PackagingLanguages.SCCMLanguagePackPackageId as PkgId

FROM Computers 
JOIN PackagingLanguages ON PackagingLanguages.Id = Computers.Language
 
WHERE Computers.Id = @ComputerId

) as t

where isnull(t.PkgId,'') &lt;&gt; ''</cmdb2sccm_softQuery>
    <cmdb2sccm_appQuery>Declare @ComputerId as bigint
set @ComputerId =  {0}

select distinct t.AppTitle from (

select PackagingLanguages.SCCMAdditionalApplication as AppTitle

FROM Computers 
JOIN PackagingLanguages ON PackagingLanguages.Id = Computers.Language
 
WHERE Computers.Id = @ComputerId

) as t

where isnull(t.AppTitle,'') &lt;&gt; ''</cmdb2sccm_appQuery>
<cmdb2sccm_varQuery>Declare @ComputerId as bigint
set @ComputerId =  {0}

select 
'Language' as name
,PackagingLanguages.CodeISO6391 as value
,'1031' as locale

FROM Computers 
JOIN PackagingLanguages ON PackagingLanguages.Id = Computers.Language
 
WHERE Computers.Id = @ComputerId

UNION ALL

select 
'ConfigMgrPrimaryUser01' as Name
,'SCCM12\TestUser1' as value
,'1031' as locale

UNION ALL

select 
'ConfigMgrColl01' as Name
,'AdditionalOSDCollection' as value
,'1031' as locale</cmdb2sccm_varQuery>
<cmdb2sccm_compUpdate>select 0</cmdb2sccm_compUpdate>

Warning

After import, make sure you have “Site” and “Configuration” configured correctly in Settings -> CMDB.

Multiple Computer Transfer Example ¶

Content will be published soon.

Tutorials for Module “CMDB”¶

In this article:

Creating Your First CMDB Class
Setting up Mass Import for ConfigMgr

Creating Your First CMDB Class ¶

For full reference see CMDB2SCCM.

Note

You have to be able to “Edit Settings”.

Go to the tab “Settings”
Navigate to CMDB and click on the plus button at the bottom

Create a new CMDB class called “Computers”:

3.1. Field Automation is used for automatic triggering of MSSQL Scripts (e.g. Stored Procedures) or external processes (e.g Powershell Scripts). See example:

<trigger>
   <afterUpdate field="" value="" 
      command=" exec sp_MyStoredProcedure @Id='{Id}' " 
   />
   <afterUpdate field="" value="" 
      title="createTicketAuto" 
      script="C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe" 
      arguments="C:\SilverMonkey\v5\Scripts\MyTriggerScript.ps1 -Id {Id}" 
      condition="{SysStatus} = A0.1 - Request" 
      restart="false" 
      back="true" 
   />
</trigger>

Create your first attributes and name them “Name” and “MACAddress”:

Create an attribute of the type “Object reference” and set the reference to another custom CMDB Class “Packaging Languages” (It will be good practice for the subsequent tutorial):

The Language class is set up as follows:

_images/Tutorial_FirstCMDBClass_6_languageclass.png

Set up naming rule

The setting name rule defines how the internal database column SysDisplayName is set. It contains important single column popups like the object reference chooser.

_images/Tutorial_FirstCMDBClass_6_namerule.png

Create a list view

Note

There are two different types of views. One is called “List” and the other one is called “Forms”. Lists display multiple elements of a CMDB Class. When clicking on an item, the configured form will be opened to view or edit the item.

Configure the list as shown:

Note

The setting detailView="Computers Details" will expect a form view with the name “Computers Details”
The setting cmdb2sccm="true" displays a transfer button in the list context menu

_images/Tutorial_FirstCMDBClass_8_preview.png

For full reference see <view> Definition

<?xml version="1.0"?>
<views>
  <view 
  splitterWidth="550" 
  detailView="Computers Details" 
  newLink="" 
  viewPane="true" 
  refresh="false" 
  excelExport="true" 
  importExport="false" 
  cmdb2sccm="true">
    <columns>
      <column field="Name" width="200"/>
      <column field="MACAddress" width="-1"/>
    </columns>
    <data>
      <condition>{search}='' OR Name like {search}</condition>
    </data>
  </view>
</views>

Create a form view

Create a new form view as shown below (you have to stick to the configured name from the list view detailView="Computers Details"):

A set of attributes and form elements are automatically suggested. You can delete the <connections link="true" /> line as no connections are configured in this example.

Add an action called “CMDB2SCCM” to the form. The final result of the form looks like this:

<views>

<view actions='true'>
<controls>
<CMDB2SCCM   
    title="Transfer Computer to SCCM" 
    param="SingleTransfer"
    restart="true"
  />
     <headline text="Computers" />
     <attribute field="Name" />
     <attribute field="MACAddress" />
     <attribute field="Language" />
     <save delete="true" />
</controls>
</view>

</views>

When you go to CMDB you can have a look at the result of our list and form:

You can add more attributes to the class and use those attributes in lists and forms as you need.

Setting up Mass Import for ConfigMgr ¶

For full reference see CMDB2SCCM.

Note

This tutorial is built up on the database schema of the tutorial Creating Your First CMDB Class.

You have to get the following information to built up an import for SCCM:

SCCM collection names the computer has to be member of
Needed computer variable names and accepted values
Knowledge of the SIM database schema

Follow the manuall ” Creating Your First CMDB Class “
Follow the ” SCCM Transfer “
Create a dummy computer and click on “Transfer computer to SCCM”

First, select “Rollout unit” (usually, rollout units only make sense when importing multiple computers; the example below is simplyfied) and click on execute

When the action is performed in SQL level the following results will be translated by the mass import feature:

Computer Query
Package Query
Application Query
Variable Query

_images/Tutorial_MassImport_02_interalquery.png

The result in SCCM looks like the following:

Variables:

Primary Users:

Collection membership:

Manual for Module “Operations”¶

In this article:

Hidden Settings
Settings
- Client Commands

Warning

This article is under construction! Please DO NOT use any of the instructions below, yet! You may cause damage to your system. This article will be finished soon.

Hidden Settings ¶

Hidden settings are configurable features that are not available through the standard configuration UI.

These settings have to be set within the Configuration.xml in a text editor.

Tip

Within the hidden settings section XPATH notation is used to give information about the correct location of the setting. Please visit this website in order to get more information on XPATH notation.

Debug Mode ¶

By setting debugmode to true a verbose log is created in app_data directory with more internal process information. Add the following XML tag to //system

1	<debugLogging>true</debugLogging>

Custom Queries ¶

Custom queries allows to use alternate queries to built up left and right side of the Operations main window.

Add the following XML nodes to //sites/site:

<CustomQueryComputers>
        <CustomQuery filterId="DefaultComputerQuery" filterLabel="All Computers" filterRole="PackWF Admin" UseSIMDB="false"><![CDATA[
          SELECT  resourceid                                         AS Id, '',
          name0                                              AS
          Computer
          ,
          user_domain0 + '\' + user_name0
          AS Username,
          obsolete0                                          AS
          Obsolete
          ,
          active0
          AS Active,
          (SELECT Count(RelationshipResourceID)
          
          
          
          FROM   v_UserMachineRelation
          WHERE  machineresourceid = v_r_system.resourceid) AS
          UserDevice
          ,overall_count = COUNT(*) OVER()
          FROM   v_r_system
          
          where v_r_system.name0 like '%{search}%'
           
          
        order by {orderby}
        
         OFFSET {start} ROWS FETCH NEXT 50 ROWS ONLY
        ]]></CustomQuery>
        <CustomQuery filterId="DefaultUserQuery" filterLabel="All Users" filterRole=""><![CDATA[
         SELECT  top 100 resourceid                                         AS Id, '',
          name0                                              AS
          Computer
          ,
          user_domain0 + '\' + user_name0
          AS Username,
          obsolete0                                          AS
          Obsolete
          ,
          active0
          AS Active,
          (SELECT Count(RelationshipResourceID)
          
          
          
          FROM   v_UserMachineRelation
          WHERE  machineresourceid = v_r_system.resourceid) AS
          UserDevice
          FROM   v_r_system
          
          where v_r_system.name0 like '%{search}%'
          
        order by {orderby}
        ]]></CustomQuery>
      </CustomQueryComputers>
      <CustomQuerySoftware>
        <CustomQuery filterId="DefaultAppQuery" filterLabel="All Applications" filterRole=""><![CDATA[
          select id, '', name, [Description] from (
SELECT '$'+CAST(CI_ConfigurationItems.CI_ID as varchar) as id, DisplayName as name, 


ltrim(SDMPackageDigest.value('declare namespace pd="http://schemas.microsoft.com/SystemCenterConfigurationManager/2009/AppMgmtDigest"; (/pd:AppMgmtDigest/pd:Application/pd:Description)[1]', 'varchar(max)')) AS [Description]



FROM CI_ConfigurationItems INNER JOIN CI_LocalizedProperties ON CI_ConfigurationItems.CI_ID = CI_LocalizedProperties.CI_ID 


WHERE CI_ConfigurationItems.CIType_ID = 10 AND CI_ConfigurationItems.IsHidden = 0 AND CI_ConfigurationItems.IsEnabled = 1 AND CI_ConfigurationItems.IsExpired = 0 AND CI_ConfigurationItems.IsLatest = 1 

)
as t

where t.name like '%{search}%' or [Description] like '%{search}%'
          
        order by {orderby}

        ]]></CustomQuery>
      </CustomQuerySoftware>

Settings ¶

Client Commands ¶

Client commands are visible in the properties dialogue in the SIM OPS module. There are different types of client commands.

WMI Query ¶

Executes SQL select on the target machine and displays the output on the website.

Example: View the services of the client including his / her status.

Setting	Value
Type	WMI query
Namespace	root\cimv2
Query	SELECT DisplayName, Description, StartMode, StartName, State FROM Win32_Service

Registry Query ¶

Reads from target machine registry and displays the output on the website.

Example: View Add Remove Programs

Setting	Value
Type	Registry query
Namespace	HKEY_LOCAL_MACHINE
Class	SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Query	DisplayName, DisplayVersion, Publisher, InstallDate

WMI Query Command ¶

Executes a specific WMI method for every returned object.

Example: Stop Windows Services with Specific Name

Setting	Value
Type	WMI Query command
Namespace	root\cimv2
Query	select * from Win32_Service where Name=’W3SVC’
Command	StopService

WMI Class Command ¶

Executes a WMI class method.

Example: Trigger SCCM HW Inventory on client

Setting	Value
Type	WMI Class command
Namespace	root\ccm
Class	SMS_Client
Command	TriggerSchedule~{00000000-0000-0000-0000-000000000001}

ClickOnce ¶

Executes local executables such as MSTSC for extended functionality regarding client systems.

Example: Start MSTSC with a Parameter

Setting	Value
Type	ClickOnce
Query	../Tools/ClickOnce/SIM_Ops_Clickonce.application?{ComputerName}

SIM_Ops_Clickonce.application is only delivered with the latest version. You can change its behaviour (executable, parameters) in the config file under “ToolsClickOnceApplication FilesSIM_Ops_Clickonce_1_0_0_0SIM_Ops_Clickonce.exe.config.deploy”.

Tip

If ClickOnce is missing in your configuration please open the Configuration.xml file and change all lines from

“query_wmi,WMI query;query_files,Filesystem;query_registry,Registry query;cmd_query_wmi,WMI query command;cmd_class_wmi,WMI class command;wol,WakeOnLAN”

to

“query_wmi,WMI query;query_files,Filesystem;query_registry,Registry query;cmd_query_wmi,WMI query command;cmd_class_wmi,WMI class command;wol,WakeOnLAN;clickonce,ClickOnce”`

Manual for Module “Webservice”¶

Warning

This article is under construction! Please DO NOT use any of the instructions below, yet! You may cause damage to your system. This article will be finished soon.

In this article:

Authentication
Available Commands

Several Microsoft ConfigMgr processes can be automated using the Web Service. This service provides the following functions that can be initiated by a corresponding Web Service call by any system:

Creating a new computer
Deleting computers
Distributing Software
Exchanging computers
Recreating computers
Creating software packages
Creating file structures
Executing scripts on the webserver

To go to the processes a HTTP POST calls the address of the service. This call is basically a stream with an XML structure that contains a set of commands. These commands are processed by the service, expanded by their results and sent back to the caller. The success status includes a new node called “result” added to the attribute “error”.

Please observe upper and lower case when you are generating the XML command structure (for example, when you enter the site code, etc.). The following example shows an XML structure with three separate commands. All calls must be made using an account that has the appropriate permissions. When the call for createation of a new computer is committed, the specified variables are added to the list of standard variables from the configuration.

Tip

Go to KB00002 - Testing the SIM Web Service Test Tool to get help connecting to the web service.

Authentication ¶

Depending on the setting of the IIS application there are two possible authentication methods:

Windows Authentication (recommended)
Authentication via XML input (supplied credentials will be used for impersonation)

 <?xml version="1.0" encoding="utf-8"?>
 <cmds>
   <login>
     <domain>DOMAIN</domain>
     <user>USERNAME</user>
     <password>ClearPassword</password>
   </login>
   <cmd></cmd>
   <cmd></cmd>
   ...
 </cmds>

Available Commands ¶

All commands sent to the webservice have to be enclosed by the following XML block:

 <?xml version="1.0" encoding="utf-8"?>
 <cmds>
   <cmd></cmd>
   <cmd></cmd>
   ...
 </cmds>

The web service executes each cmd element and adds a result node to it.

 <?xml version="1.0" encoding="utf-8"?>
 <cmds>
   <cmd>
     <param1></param1>
     <param2></param2>
     <param3></param3>
     <result error="true/false">Message</result>
   </cmd>
   <cmd></cmd>
   ...
 </cmds>

Deployment ¶

Creating a deployment for a ConfigMgr package. Go to websrv-assignment in order to get help deploying a ConfigMgr application.

 <cmd name="deployment" siteCode="000">

   <computerName>Name of the computer</computerName><!-- Supply NAME -->
   <resourceID>Resource ID of the computer</resourceID><!-- or resourceID -->

   <packageName>Supplied value of the field "Name" in ConfigMgr console</packageName><!-- Supply NAME -->
   <packageID>Id of the package</packageID><!-- or packageID -->

   <program>name of the package program</program>
   <type>Optional/Mandatory</type>

 </cmd>

Note

Depeding on the settings of Settings->Sites->[SITE]->Computer software deplyoment, corresponding collections and deployments will be created in ConfigMgr. The same settings are used by the Operations module.

Examples

Creating a deployment of a SCCM package by IDs

 <?xml version="1.0" encoding="utf-8"?>
 <cmds>
   <cmd name="deployment" siteCode="P01">
     <computerName></computerName>
     <resourceID>12341134</resourceID>
     <packageName></packageName>
     <packageID>P0100001</packageID>
     <program>install</program>
     <type>Mandatory</type>
   </cmd>
 </cmds>

Creating a deployment of a SCCM package by names

 <?xml version="1.0" encoding="utf-8"?>
 <cmds>
   <cmd name="deployment" siteCode="P01">
     <computerName>MyPc1</computerName>
     <resourceID></resourceID>
     <packageName>TestPackage</packageName>
     <packageID></packageID>
     <program>install</program>
     <type>Mandatory</type>
   </cmd>
 </cmds>

deleteClient ¶

<cmd name="deleteClient" siteCode="000">
  <resourceID>Resourcen ID des Computers (alternativ)</resourceID>
  <name>Name des Computers (alternativ)</name>
</cmd>

createClient ¶

<cmd name="createClient" siteCode="000">
  <name>Computername</name>
  <mac>MAC Adresse</mac>
  <configuration>Standard</configuration>
  <overwrite>true</overwrite>
  <variable>
    <name>Variablenname</name>
    <locale>Locale</locale>
    <value>Variablenwert</value>
 </variable>
</cmd>

executeScript ¶

<cmd name="executeScript" siteCode="000">
 <executable>Computername</executable>
 <parameters>MAC Adresse</parameters>
</cmd>

exchangeClient ¶

<cmd name="exchangeClient" siteCode="000">
  <sourceComputerName>Name des alten Computers</sourceComputerName>
  <targetComputerName>Name des neuen Computers (alternativ Name oder MAC)</targetComputerName>
  <targetComputerMAC>MAC Adresse des neuen Computers (alternative Name oder MAC)</targetComputerMAC>
  <configuration>Name der Konfiguration des neuen Computers</configuration>
  <packages>
      <packageId>PaketId des ersten Paketes</packageId>
      <packageId>PaketId des zweiten Paketes</packageId>
  </packages>
  <applications>
      <application>Name der Applikation</application>
      <application>Name der Applikation</application>
  </applications >
 <variable>

    <name>Variablenname</name>
    <locale>Locale</locale>
    <value>Variablenwert</value>
 </variable>
</cmd>

refreshClient ¶

assignment ¶

Creating a deployment for a ConfigMgr application. Go to Deployment for deploying a ConfigMgr package.

<cmd name="assignment" siteCode="000">
 <computerName>Name des Computers (alternativ)</computerName>
 <resourceID>Resourcen ID des Computers (alternativ)</applicationID >
 <applicationID>ApplikationsID</ applicationID>
 <type>Installation|Deinstallation</type>
 <offerTypeId>0=Required|2=Available</offerTypeId>
</cmd>

createFileStructure ¶

<cmd name="createFileStructure">
 <packagingParamName1>Wert 1</packagingParamName1>
 <packagingParamName2>Wert 2</packagingParamName2>
 <packagingParamName3>Wert 3</packagingParamName3>
 ...
</cmd>

createPackage ¶

<cmd name=" createPackage">
 <packagingParamName1>Wert 1</packagingParamName1>
 <packagingParamName2>Wert 2</packagingParamName2>
 <packagingParamName3>Wert 3</packagingParamName3>
 ...
</cmd>

createApplication ¶

<cmd name="createApplication" siteCode="000" template="default" >
  <variable name="Name">Wert</variable>
</cmd>

createCollection ¶

<cmd name="createCollection" siteCode="000"
 name="Neu 2"
 collectionType="1=user|2=device"
 limitToCollectionId="SMS00001"
 query="" />
</cmd>

Manual for Module “Packaging”¶

Warning

This article is under construction! Please DO NOT use any of the instructions below, yet! You may cause damage to your system. This article will be finished soon.

In this article:

General Information
Sites
- Copy Jobs
- Packaging Parameters
Programmes
Operating System Groups
Attributes
Views

General Information ¶

The Packaging Module is used to map and standardize the organisational packaging process. In addition, it is possible to use operations to simplify Configuration Manager tasks like creating packages or applications. The Packaging Module is based on the functions of the CMDB Module: attributes, views and operations are configured just as in the CMDB Module. The settings for the automatic creation of packages in SCCM (System Center Configuration Manager) and the creation of folder structures for the packaging process are described in the sections Sites, Programmes and Operating System Groups.

Property	Description
Table name	The name of the packaging table.
Name rule	Defines how packages will be displayed in connection views from other classes.
Automation	Defines triggers that will execute SQL Stored Procedures on specific events.
Workflow	Defines the preconfigured workflow for the packaging process.
Key field	Defines the identifier for the packaging table.
Link view	Defines the view that will be displayed when you open an entry of the packaging table from another class form.

Sites ¶

Property	Description
Name - de	Displayed German name of the packaging site.
Name - en	Displayed English name of the packaging site.
Site	Choose a preconfigured site as packaging site here. See the reference below to learn how to configure sites in general.
Package Folder	Depricated!(Feature for SCCM Packages)
Package Name rule	Depricated!(Feature for SCCM Packages)
Analyse file ext.	Define what kind of files should be parsed when copy jobs are executed. All files that are copied and that have a type that is defined here will be parsed, meaning when there are Attributenames in curly brackets ({AttributeName}) they will be replaced with the attribute value in the form context. (Possible values: “docx; vbs; txt; xml”)

See Sites to learn how to configure sites.

Copy Jobs ¶

Various file copying operations can be defined for the packaging process. Create the filestructure for the packaging process with this operation. Then execute single or multiple copy jobs from the forms.

Property Description

Name - de Displayed German name of the copy job.

Name - en Displayed English name of the copy job.

Source Source path for the copy job.

Destination Destination path for the copy job.

See the general Site Configuration for the definition of the files that will be parsed while executing copy jobs.

Note

Copy jobs will be executed in the context of the deposited SCCM account.

Packaging Parameters ¶

This feature is depricated!(Feature for SCCM Packages)

Programmes ¶

This feature is depricated!(Feature for SCCM Packages)

Operating System Groups ¶

This feature is depricated!(Feature for SCCM Packages)

Attributes ¶

Create attributes for the packaging workflow here.

You can see informations about attributes under Attributes.

Views ¶

Create lists and forms for the packaging workflow here.

For further information see Form Definition.

Manual for Module “Portals”¶

Warning

This article is under construction! Please DO NOT use any of the instructions below, yet! You may cause damage to your system. This article will be finished soon.

In this article:

Column
Widgets
Portal Rights

Portals are used to define start or overview pages. A portal can have multiple columns with multiple widgets. Every portal can be restricted to a role. You can use different widgets here: SQL Querys, Links and Reports.

Column ¶

Property	Description	Example
Border top	Property that defines the vertical top-margin of the column.	25
Border right	Property that defines the horizontal right-margin of the column.	25
Border bottom	Property that defines the vertical bottom-margin of the column.	25
Border left	Property that defines the horizontal left-margin of the column.	25

Note

Do not let your widget XML-definition start with a blank space! This is a common error - the widget will not function properly.

Widgets ¶

SQL Query ¶

<sqlQuery
  database=""
  query="SELECT TOP 10 SysDisplayName, Name, Id AS _Id
  FROM Computer"
  link="Support/TypeView.aspx?TypeView=Computer
  Details&Id={_Id}"
  size="400;250"
  refresh="true"
 />

Links ¶

<links>
 <link de="Google de" en="Google en" url="http://www.google.de" />
 <link de="Google de" en="Google en" url="http://www.google.de" />
</links>

localreport ¶

<localReport
id=""
name="Issues"
/>

Portal Rights ¶

To set a portal right, click the “+ portal right”-button and choose the desired role, finally click save.

Manual for Module “Reporting”¶

Warning

This article is under construction! Please DO NOT use any of the instructions below, yet! You may cause damage to your system. This article will be finished soon.

Site custom reports can be stored within this configuration area. The reports have to be submitted in the form of RDL or RDLC files (format of Microsoft Reporting Services). Reports can be generated most easily with the Microsoft Business Intelligence Development Studio. After uploading a report definition file, the data sources in the report are analyzed and displayed. When you create a report you have to assign report authorization groups, which may open this report. You can define custom folder structures to structorize multiple reports.

Property	Description	Example
Name	Localized Name of the report	Report1
URL	Reference to an external report	25
Definition	Report definition file	MyReport.rdl
Connection	Database Connection String (if you want query a different database that the SIM Database or rather no linkserver to the specific database has been created within the SIM database server	25
Dataset 1 .. n	SQL query for all datasets within the report	SELECT Table.Column,Table.Column2 FROM Table
Show toolbar	Report definition file	0/1
Show toolbar navigation	Check to generally display the toolbar within the report	0/1
Show toolbar zoom	Check to show toolbar zoom	0/1
Show toolbar search	Check to show toolbar search	0/1
Show toolbar export	Check to show toolbar export	0/1
Show toolbar refresh	Check to show toolbar refresh	0/1
Show toolbar print	Check to show toolbar print	0/1

Knowledge Base¶

Contents:

KB00001 - Silver Monkey Database Backup¶

Please follow the instructions below to create a backup of the Silver Monkey database. This document is a quickstart for administrators who are not familiar with SQL Management Studio.

KB00002 - Testing the SIM Web Service Test Tool¶

In this article:

Downloading Web Service Test Tool
Extracting Content
Editing start.cmd File

There is a command line tool which enables administrators to perform an easy test without any knowledge about HTTP web service technology.

Downloading Web Service Test Tool ¶

Command line test-tool download.
GUI test-tool download.

Extracting Content ¶

Extracting the content of the ZIP:

The sample XML file will create a simple computer with one variable:

<?xml version="1.0" encoding="utf-8"?>
<cmds>
	<cmd name="createClient" siteCode="P01">
		<overwrite>true</overwrite>
		<name>WebSrvPC{Var1}</name>
		<mac>FC:BB:00:11:00:{Var1}</mac>
		<configuration>Win10x64</configuration>
		<variable>
			<name>FQDN</name>
			<locale>1033</locale>
			<value>domain.dom</value>
		</variable>
	</cmd>
	<cmd name="executeScript">
		<executable>C:\Windows\System32\cmd.exe</executable>
		<arguments>
			<argument>/C echo Var1: {Var1} >C:\temp\WebServiceLog{Var1}.txt</argument>
		</arguments>
	</cmd>
</cmds>

Editing start.cmd File ¶

The start.cmd file is meant to be an example of how to start the web service test tool.

An example for the command line could be:

WebServiceTestCmdLine.exe /XMLFilePath:"C:\temp\sample.xml" /WebServiceURL:"http://webserver/sim/servicelogin/service.aspx" /Var1:"01"

Running the command results in a log file written beside the EXE:

+ Ok | Starting Silver Monkey Web Service Tester | 27.07.2016 11:15:45
++ Ok | Sending command to "http://webserver/sim/servicelogin/service.aspx". | 27.07.2016 11:16:16
+++ Ok | Result: <?xml version="1.0" encoding="utf-8"?><cmds><cmd name="createClient" siteCode="P01"><overwrite>true</overwrite><name>WebSrvPC01</name><mac>FC:BB:00:11:00:01</mac><configuration>Win10x64</configuration><variable><name>FQDN</name><locale>1033</locale><value>domain.dom</value></variable><result error="false">Operation completed. Existing machine was overwritten</result></cmd><cmd name="executeScript"><executable>C:\Windows\System32\cmd.exe</executable><arguments><argument>/C echo Var1: 01 &gt;C:\temp\WebServiceLog01.txt</argument></arguments><result> Process was executed with following exit Code: 0 </result></cmd></cmds> | 27.07.2016 11:16:44

Tip

The Parameters /Var1 to /Var5 are optional and are used to replace corresponding {Var1} to {Var5} template variables in the XMLFile.

KB00003 - Setting Up Fixed WMI Ports¶

Setting Up Dynamic Port Allocation¶

Please click here in order to access the tutorial on the determination of dynamic port allocation in Windows.

Download script for port allocation setup

Determining Port for Endpoint¶

Launch DCOMCNFG.EXE and follow the instructions below.

Changing WMI Mode¶

Please click here in order to get access to the detailed tutorial and follow the instructions on the website.

Restart¶

Please restart the system.

Test Script¶

Type in your IP/user/password in the script below.

Download test script

Note

Due to eventually blocked Kerberos ports, some DNS names might not work. In this case, please use the IP adress of the target system only.

Expected return value (the site display name has to be displayed):

KB00004 - Restoring SIM Database¶

In this article:

Creating a New Database
Running Script

Creating a New Database ¶

Connect to your SQL Server via SQL Management Studio and create a new Database:

In the following dialogue, choose a database name that fits your naming convention. Click the ‘OK’-button.

Then give authorization following the installation guide.

Running Script ¶

Choose ‘New Query’:

Copy the content of the SQL backup file that is part of the installation package and paste it into the new query window. Replace the name of the database in the ‘USE {DATABASE NAME}’ part of the query with the name of the database you just created.

After (!) this click the ‘Execute’ button.

You have successfully restored the SIM Database!

KB00005 - Resetting SIM Packaging Jobs¶

In this article:

Erasing the Table of Packaging Jobs
Resetting Identity

Erasing the Table of Packaging Jobs ¶

Resetting Identity ¶

Excecute the following command in order to make the database start the new packaging jobs with the ID number 1.

“DBCC CHECKIDENT(‘PackagingJob’, RESEED, 0)” (without quotation marks).

KB00006 - Establishing SCCM FolderID¶

In this article:

Script Configuration
Starting the Script

Script Configuration ¶

Get SCCM FolderID - Script.

A filled in form should be displayed similar to the image below:

Starting the Script ¶

Open cmd.exe and read out the ID as shown in the red box below.

KB00007 - Creating an IIS Website for Silver Monkey¶

In this article:

Copying Files to Inetpub
Creating an Application
Setting up Writing Permission for App_data
Inserting Configuration.xml
Testing your Website

Copying Files to Inetpub ¶

Create a new folder in

C:\inetpub\wwwroot\

Please be sure to name your file with rising numbers following the name convention “treon_R****” if a Silver Monkey website already exists (see image below).

Now, move the content of the Silver Monkey installation file to the folder you just created.

Creating an Application ¶

Please start MMC for IIS (Microsoft Internet Information Services). Right click on the folder and select “Add Application”.

Fill in the fields displayed. The field named “Alias” should be filled with “Treon_R0001”.

Note

Please choose the application pool named “Treon” or “SIM” if it exists.

In the next step, please authenticate the application by activating its authentication for Windows.

Setting up Writing Permission for App_data ¶

Writing permission can be set under

C:\inetpub\wwwroot\treonR0001\App_Data

Inserting Configuration.xml ¶

Please copy the file “configuration.xml” from the former website to the new one.

Testing your Website ¶

Note

In case of a disabled Single Sign On, please restart Internet Explorer before restarting the whole server.

Open Internet explorer, then go to “http://SERVERNAME/Treon_R0001” .

Check your website version as follows:

KB00008 - Sending an Email in PackWF at the Push of a Button¶

In this article:

XML Format

XML Format ¶

<sendMail
  from="noreply@phatconsulting.de"
  to="{$MAIL>PackageResponsible}"
  subject="Software Packaging: {RequestManufacturerName} {RequestProductName} ({RequestID})"
  body="Hallo, &lt;br /&gt;bitte Paket und Installationsanleitung hier ablegen: 
		&lt;br /&gt;&quot;{RequestTransferPath}&quot;
		&lt;br /&gt;
		&lt;br /&gt;
		&lt;a href=&quot;http://phatsrv046/treon_r0005/Support/TypeView.aspx?PopUp=true&amp;TypeViewId=46&amp;Id={Id}&quot;&gt;Auftrag einsehen&lt;/a&gt;
		&lt;br /&gt;
		&lt;br /&gt;
		Mit Freundlichen Gr&#252;&#223;en
		&lt;br /&gt;
		Software Packaging Team" />

If you would like to use HTML in the main body as shown in the example above, you will have to encode it. This website will facilitate your work as shown in the example below.

KB00009 - Computer Refresh - AdminHowTo¶

In this article:

Preparing Settings
Refreshing your Computer - Examples

Preparing Settings ¶

The prefix for packages and applications can be determined in the SCCM settings.

Note

Packages support up to 999 variables. This is the reason why “###” is displayed.

Applications usually support up to 99 variables. This is why “##” is displayed in the coresponding field.

Refreshing your Computer - Examples ¶

Under “packages” you will find all SCCM packages which either

have been announced on the computer (status is directly read out of SCCM)

or

have been resolved by the existing variable (packaging IDs are compared to live data in SCCM).

SCCM applications which are displayed under “Applications” are displayed in the same way as SCCM packages.

As soon as the button “execute” is clicked, the existing computer object is going to be deleted in SCCM and a new one with the same name and MAC adress will be created. The properties of this new computer object will show a corresponding variable for each package and each application.

KB00010 - Adjusting the IIS IDLE Timeout¶

First, please start the IIS Console, choose the Silver Monkey Application and open the Session State Configuration.

We recommend setting a timeout value of 960 minutes (i.e. 16 hours):

KB00011 - Changing IIS App Pool to Service User¶

In this article:

Creating App Pool
Connecting App Pool with the Application

Creating App Pool ¶

Please start IIS (i.e. Internet Information Services) Console and choose the node called “Application Pools”. Then perform a right-click and choose “Add Application Pool…”. Follow the instructions below.

Connecting App Pool with the Application ¶

Right-click on the Application you would like to connect with…

KB00012 - Full SQL Connection Pool¶

In this article:

Adjusting Web.Config

Adjusting Web.Config ¶

You will find the Web.Config file in

C:\inetpub\wwwroot\[TreonWesite].

Please open the file in a text editor and search for the section “<appSettings>”.

Silver Monkey connects to at least two different SQL databases:

Its original Silvermonkey SQL database
The SCCM Site database

Depending on which Connection Pool fills up first, either TreonConnectionString* or SiteConnectionString* will have to be adjusted. Especially, pay attention to the last part of the Connection String:

You will have to add the following code or rather adjust its value to “500” if it doesn’t already exist in the Connection String (the value is set to “100” by default):

;max pool size=500

Both Connection Strings, *SQL as well as *Windows have to be changed.

For further Information about Connection String, please visit this website .

KB00013 - Activating and Updating License Key¶

In this article:

Activating or Updating the Activation Key via the User Interface
Activating or Updating the Activation Key in the Configuration.xml

Activating or Updating the Activation Key via the User Interface ¶

Note

Silver Monkey Administrator rights are required to activate or update the license key via the user interface. If the “Settings”-Tab is visible, you have the required rights.

In the settings, fill in the field named ‘Activation code’ with the license key that is part of the license certificate.

Afterwards click the ‘Save’-button.

Note

The new license key cannot be activated until you restart the IIS Service and the Silver Monkey Web Application Server!

Activating or Updating the Activation Key in the Configuration.xml ¶

If you do not have direct access to the settings in the user interface, set the activation key in the Configuration.xml:

Warning

Before changing Configuration.xml please create a safety-copy!

The configuration.xml is located in the web application server in the following directory:

C:\inetpub\wwwroot\SIM_R****\App_Data

Fill in the field “<activationCode>” with the license key:

Note

The new license key will not be activated until you restart the IIS Service and the Silver Monkey Web Application Server.

KB00014 - Finding Log Files and ‘Configuration.xml’¶

In this article:

Finding Log Files
Finding the Configuration.xml File
Taking Screenshots of Error Messages

Finding Log Files ¶

The log files will be found in the system providing the IIS service in one of the following directories:

C:\inetpub\wwwroot\treon_r****\App_Data\Logs
C:\inetpub\wwwroot\sim_r****\App_Data\Logs

Finding the Configuration.xml File ¶

Search for the Configuration.xml file in the same system in one of the following directories:

C:\inetpub\wwwroot\treon_r****\App_Data
C:\inetpub\wwwroot\sim_r****\App_Data

Please equally send a copy of Configuration.xml to support@treon.de .

Taking Screenshots of Error Messages ¶

We would also like to ask you to send us screenshots of error messages, problems or eventually displayed requirements.

Tip

Feel free to combine log files, Configuration.xml and screenshots in a single email.

KB00015 - Creating a System Report¶

In this article:

Downloading Report Builder
Selecting Server and Database

Downloading Report Builder ¶

Please visit this website, download and install Report Builder.
Then, follow the instrucions shown on the images below.

Selecting Server and Database ¶

KB00016 - Reinitializing AD Sync¶

In this article:

Starting IIS Application Pool Recycle
Finding Configuration.xml
Resetting AD Sync Timer
Starting and Checking AD Sync

Starting IIS Application Pool Recycle ¶

In order to discern the configurated App Pool, please follow the instruction below:

Then, start recycling:

Finding Configuration.xml ¶

Search for the Configuration.xml file in the system that delivers the IIS service in one of the following directories:

C:\inetpub\wwwroot\treon_r****\App_Data
C:\inetpub\wwwroot\sim_r****\App_Data

Resetting AD Sync Timer ¶

For example, set the value to one year in the past. Then save the file.

Starting and Checking AD Sync ¶

Please reload the Silver Monkey website in your browser by pressing the F5-key. A new AdSync log file should be created in the log directory.

KB00017 - Configuration Manager Rights¶

In this article:

ConfigMgr WMI API
SQL Rights

ConfigMgr WMI API ¶

Import a role via the following xml File (zipped).

See Dowload XML.

After this entitle a corresponding user with this role.

SQL Rights ¶

The following SQL rights have to be set for the Silver Monkey SCCM SQL DB Service Account:

KB00018 - SCCM OS Notation¶

In this article: OS Notion for

Android
iOS/iPad
Mac
Mobile/Symbian
Windows XP, Vista, 7, 8 and Windows Server
Windows Mobile
Windows Phone
Windows 10

Android ¶

“Android/All_Android”,
“Android/Android_4_0”,
“Android/Android_4_1”,
“Android/Android_4_2”

iOS/iPad ¶

“iOS/iPad”,
“iOS/iPad_5”,
“iOS/iPad_6”,
“iOS/iPad_7”,
“iOS/iPad_8”,
“iOS/iPhone”,
“iOS/iPhone_5”,
“iOS/iPhone_6”,
“iOS/iPhone_7”,
“iOS/iPhone_8”

Mac ¶

“Mac/All_Mac_10_10”,
“Mac/All_Mac_10_6”,
“Mac/All_Mac_10_7”,
“Mac/All_Mac_10_8”,
“Mac/All_Mac_10_9”

Mobile/Symbian ¶

“Mobile/All_Mobile”,

“Symbian/All_Symbian”

Windows XP, Vista, 7, 8 and Windows Server ¶

“Windows/All_ARM_Windows_8.1”,
“Windows/All_ARM_Windows_8.1_Client”,
“Windows/All_ARM_Windows_8_Client”,
“Windows/All_Embedded_Windows_XP”,
“Windows/All_IA64_Windows_Server_2003_Non_R2”,
“Windows/All_IA64_Windows_Server_2008”,
“Windows/All_Windows_Client_Server”,
“Windows/All_Windows_RT”,
“Windows/All_x64_Windows_7_Client”,
“Windows/All_x64_Windows_8.1”,
“Windows/All_x64_Windows_8.1_and_higher_Clients”,
“Windows/All_x64_Windows_8.1_Client”,
“Windows/All_x64_Windows_8_and_higher_Client”,
“Windows/All_x64_Windows_8_Client”,
“Windows/All_x64_Windows_Embedded_8.1_Industry”,
“Windows/All_x64_Windows_Embedded_8_Industry”,
“Windows/All_x64_Windows_Embedded_8_Standard”,
“Windows/All_x64_Windows_Server_2003_Non_R2”,
“Windows/All_x64_Windows_Server_2003_R2”,
“Windows/All_x64_Windows_Server_2008”,
“Windows/All_x64_Windows_Server_2008_R2”,
“Windows/All_x64_Windows_Server_2012_R2”,
“Windows/All_x64_Windows_Server_2012_R2_and_higher”,
“Windows/All_x64_Windows_Server_8”,
“Windows/All_x64_Windows_Server_8_and_higher”,
“Windows/All_x64_Windows_Vista”,
“Windows/All_x64_Windows_XP_Professional”,
“Windows/All_x86_Windows_7_Client”,
“Windows/All_x86_Windows_8.1”,
“Windows/All_x86_Windows_8.1_and_higher_Clients”,
“Windows/All_x86_Windows_8.1_Client”,
“Windows/All_x86_Windows_8_and_higher_Client”,
“Windows/All_x86_Windows_8_Client”,
“Windows/All_x86_Windows_Embedded_8.1_Industry”,
“Windows/All_x86_Windows_Embedded_8_Industry”,
“Windows/All_x86_Windows_Embedded_8_Standard”,
“Windows/All_x86_Windows_Server_2003_Non_R2”,
“Windows/All_x86_Windows_Server_2003_R2”,
“Windows/All_x86_Windows_Server_2008”,
“Windows/All_x86_Windows_Vista”,
“Windows/All_x86_Windows_XP”,
“Windows/IA64_Windows_Server_2003_SP1”,
“Windows/IA64_Windows_Server_2003_SP2”,
“Windows/IA64_Windows_Server_2008_original_release”,
“Windows/IA64_Windows_Server_2008_SP2”,
“Windows/x64_Embedded_Windows_7”,
“Windows/x64_Windows_7_Client”,
“Windows/x64_Windows_7_SP1”,
“Windows/x64_Windows_Server_2003_R2_original_release_SP1”,
“Windows/x64_Windows_Server_2003_R2_SP2”,
“Windows/x64_Windows_Server_2003_SP1”,
“Windows/x64_Windows_Server_2003_SP2”,
“Windows/x64_Windows_Server_2008_Core”,
“Windows/x64_Windows_Server_2008_original_release”,
“Windows/x64_Windows_Server_2008_R2”,
“Windows/x64_Windows_Server_2008_R2_Core”,
“Windows/x64_Windows_Server_2008_R2_SP1”,
“Windows/x64_Windows_Server_2008_R2_SP1_Core”,
“Windows/x64_Windows_Server_2008_SP2”,
“Windows/x64_Windows_Server_2008_SP2_Core”,
“Windows/x64_Windows_Vista_Original_Release”,
“Windows/x64_Windows_Vista_SP1”,
“Windows/x64_Windows_Vista_SP2”,
“Windows/x64_Windows_XP_Professional_SP1”,
“Windows/x64_Windows_XP_Professional_SP2”,
“Windows/x86_Embedded_Windows_7”,
“Windows/x86_Windows_7_Client”,
“Windows/x86_Windows_7_SP1”,
“Windows/x86_Windows_Server_2003_R2_original_release_SP1”,
“Windows/x86_Windows_Server_2003_R2_SP2”,
“Windows/x86_Windows_Server_2003_SP1”,
“Windows/x86_Windows_Server_2003_SP2”,
“Windows/x86_Windows_Server_2008_Core”,
“Windows/x86_Windows_Server_2008_original_release”,
“Windows/x86_Windows_Server_2008_SP2”,
“Windows/x86_Windows_Vista_Original_Release”,
“Windows/x86_Windows_Vista_SP1”,
“Windows/x86_Windows_Vista_SP2”,
“Windows/x86_Windows_XP_Professional_Service_Pack_2”,
“Windows/x86_Windows_XP_Professional_Service_Pack_3”

Windows Mobile ¶

“WindowsMobile/All_Windows_Mobile”,
“WindowsMobile/Windows_Mobile_6.1”,
“WindowsMobile/Windows_Mobile_6.5”

Windows Phone ¶

“WindowsPhone/All_Windows_Phone”,

“WindowsPhone/Windows_Phone_8”

Windows 10 ¶

“Windows/All_x64_Windows_10_and_higher_Clients”

KB00019 - Installing and Configurating SQL¶

Please follow the instructions below to install and configurate your SQL.

KB00020 - SIM SQL Database Rights¶

Creating the SIM Service Account¶

Open SQL Management Studio and connect to your Silver Monkey SQL DB server. Expand ‘Security’ and right click ‘Login’ to create a new login.

Choose a name (e.g. ‘sql-sim’) and a password. Set the authentication to ‘SQL Server authentication’ and uncheck the ‘Enforce password policy’-checkbox.

Navigate to ‘User Mapping’ choose the SIM SQL DB and activate the db_owner role. After that click ‘OK’.

You now have successfully created your SIM Service Account!

KB00021 - Disabling AD Sync¶

To disable AD Sync (which is performed every 12 hours by the first website visitor) simply follow the steps below.

1. Finding configuration.xml¶

Further information on how to find the Configuration.xml file, read the corresponding article. ( KB00014 - Finding Log Files and ‘Configuration.xml’ )

2. Changing Date to Future Date¶

  <system>
    ...
    <directoryCacheInterval>12</directoryCacheInterval>
    <lastDirectoryScan>8/10/3016 10:03:34 AM</lastDirectoryScan>
	...

KB00022 - Known Issues¶

This means that the service account for SCCM has to be local admin on the SCCM server in order to set up a functioning WMI connection.

Solve this problem by following the instructions below:

KB00023 - Copy Files fix Documentparsing¶

These curly underlinings represent the grammatical markup of Word. This markup can prevent the copyfiles function from working correctly.

Solve this problem by following the instructions below:

KB00024 - Create Serverlink with Alias and withCreds¶

Use this sample SQL script to create an SQL serverlink to the wanted server. You can specify an alias and credetials in this script, default placeholders in the name of the linkedserverobject can be used to reference different sitenames.

-- Creates an SQL Server Link to the specified Server, provides an Alias with 'XXX' as placeholder for an Suffix. Specify an SQL User that is used for the Connection in the last lines.

USE [master]
GO
EXEC master.dbo.sp_addlinkedserver @server = N'SIM_CONFIGMGR_XXX', @srvproduct=N'sql_server', @provider=N'SQLNCLI11', @datasrc=N'SQLSERVERNAME'
-- Specify SQL Servername like this "simserver,1433" or specify the instance via backslash. 
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'rpc', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'rpc out', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'use remote collation', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'SIM_CONFIGMGR_XXX', @optname=N'remote proc transaction promotion', @optvalue=N'true'
GO
USE [master]
GO
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname = N'SIM_CONFIGMGR_XXX', @locallogin = NULL , @useself = N'False', @rmtuser = N'SQLUSERNAME', @rmtpassword = N'SQLUSERPASSWORD'
GO

Changelog¶

Version	TicketId	Product	Description
5.69	020407	v5 Kernel	User Variable more output types:$USERNAME$ESCAPEDUSERNAME
5.69	020409	v5 Software Packaging	new Entry Button with labelNewLinkLabel=’Label’
5.69	020410	v5 Software Packaging	copyFiles keeps encoding of copied files
5.69	020411	v5 Software Packaging	Optimized Comment icon
5.69	020405	v5 Software Packaging	createCollection loaded wrong definition from other view
5.69	020406	v5 Software Packaging	createCollection now support for directMembership (add&remove)
5.69	020412	v5 System Operations	Application dialog shows sccm package id
5.67	020401	Web Service	Added Feature for dynamic resolve of Computer variables to deployment
5.66	020403	v5 Kernel	checkCondition für ExecuteTriggerEvent ist jetzt zusammen mit Email jetzt möglich
5.66	020393	v5 Kernel	Sim can execute scripts on SQL Events (oncreate, afterDelete, etc).
5.66	020386	v5 Kernel	Advanced Filter Options for MultiSelect
5.66	020385	v5 Self Service	Support for SCCM Fast Channel
5.66	020390	v5 Software Packaging	SetDefaultOnSave korrigiert
5.66	020397	v5 Software Packaging	Step Conditions (Plausibility) also Support roles
5.66	020400	v5 Software Packaging	SendMail ist jetzt automatisch über SIM möglich ohne SQL Trigger. OnUpdate (save oder statuswechseln)
5.65	020380	v5 Self Service	Added SCCM Fast Channel Option for Shop
5.65	020381	v5 Self Service	Added DirectLink for Shop
5.64	020378	v5 Kernel	CMDB Function for the mass Import of systems
5.64	020337	v5 Software Packaging	TextBoxes allow clickable paths
5.63	020324	v5 Kernel	-Selected Day will be highlighted
5.63	020333	v5 Kernel	Object reference allows 3 Arguments. Example: @OBJ.Package.Language.ISO631
5.63	020318	v5 Software Packaging	removePlus für Verbindungen verfügbar
5.63	020328	v5 Software Packaging	SetDefaultOnLoad also working for Objects and Data Lists
5.63	020367	v5 Software Packaging	<list> elements support link to another views with dynamic variables
5.63	020368	v5 Software Packaging	hide Connections available. Only useful when having a list right after it.
5.63	020372	v5 Software Packaging	Now possible to set Logical condition for a certain step. Use ‘plausibility’
5.63	020329	v5 System Operations	Customized View Create Computer From Old (with customized Variables)
5.62	020312	v5 Software Packaging	Fixed issue that CreateApplication looked not for newest application title for checking existence.
5.61	020293	Miscellaneous	Cancel Button in ‘addUserToDevice’ works normal.
5.61	020294	Miscellaneous	Bug with the multiselector in CMDB was resolved.
5.61	020295	Miscellaneous	The list at the left side will be updated right when objects are removed in CMDB
5.61	020298	v5 Kernel	Changed GUI to new Silver Monkey CI
5.61	020305	v5 Kernel	new filter for CMDB
5.61	020300	v5 Software Packaging	If the collection already exists the ‘createCollection’ command will add a deployment.
5.61	020301	v5 Software Packaging	Change information from existing applications with createApplication command.
5.61	020303	v5 System Operations	Domain will be also shown with the username in Operations
5.61	020306	v5 System Operations	More than one site in operations module.
5.61	020296	v5 System Operations	More than one Computer objects can be selected to be assigned to a user.
5.60	020289	Miscellaneous	Fixed issue cannot create application (Unhandled exception).
5.60	000267	v5 Kernel	Automatic update of configuration.xml is possible, now
5.60	010287	v5 Software Packaging	Created a new XML attribute called ‘hide’ for form elements.
5.60	020287	v5 Software Packaging	Fixed issue: Error while creating Application Connot access AppVPackageFolder
5.60	020288	v5 Software Packaging	Fixed issue with using wrong credentials for CopyFiles command
5.59	010283	v5 Kernel	Fixed issue: Import/Export does not support XLSX files with multiple sheets
5.58	010281	v5 System Operations	Primary User Support for CreateComputer
5.57	010273	v5 Self Service	Fixed issue with missing user impersonation for local SCCM connections.
5.57	010274	v5 Self Service	Fixed issue with Shop references to Applications. Now, a permanent ID is used and Applications can be edited after adding them to the shop.
5.56	010272	v5 System Operations	Keep Primary User when using Computer Exchange/Refresh
5.55	010271	v5 Self Service	Es können die Shop Produkte dynamisch aus den PackagingJob Datensätzen generiert werden
5.53	000259	Miscellaneous	Count of all connected SCCM sites visible in configuration
5.53	000268	v5 Kernel	Import durch XLSX immer gleicher SysDisplayName
5.52	000227	v5 System Operations	Primary users can be managed through objects, now.
5.52	000199	Web Service	Extended the function of ‘Create Client’ by’overwrite=true’ that is Controlling if there is a Computer with the same Name/MAC and whether or not it should be deleted.
5.51	000226	v5 Rollout Center	Dynamic target collections and primary users are avalible now.
5.48	000160	v5 System Operations	it is now possible to choose the MAC addresses by drop down in the ‘Refresh Computer’ dialog.
5.41	000253	Miscellaneous	It’s possible to use the FORMAT function when referencing on an @OBJ function.
5.41	000209	v5 Kernel	It’s now possible to set a datalist attribute as valid.
5.41	000185	v5 Kernel	It is possible to activate the date picker in english, now.
5.41	000187	v5 Kernel	Fixed a bug that caused varchars bigger than 800 not to be saved.
5.41	000191	v5 Kernel	Treon variables now support referenced objects ( for example: {@OBJ.PackageLanguage.CodeISO6392}).
5.41	000194	v5 Kernel	Adjusted dropdown fields, enabled the option to edit the specified column.
5.41	000196	v5 Kernel	Fixed Timing problem through MARS, parallel database queries function properly again.
5.41	000245	v5 Self Service	Fixed a bug in the shop module that prohibits adding members and deploying.
5.39	000184	v5 Kernel	Defined filters for active Directory users globally. Filter supports variables from the Job table.
5.39	000173	v5 Kernel	Fixed a bug that prohibited the ‘packet commandline Install’ field to be displayed correctly.
5.39	000175	v5 Kernel	Defining impersonation as Shared, decimate multiple registrations. Stabilization of impersonation. Minimized database accesses to spare connection pool.
5.39	000176	v5 Kernel	Enabled triggering multiple domains in the active directory fields. Extended filter of the formular attributes.
5.39	000177	v5 Kernel	Optimized database Access: Adjusted impersonification.
5.39	000179	v5 Kernel	Adjusted HW Hey algorithm. The Domain of the IIS System is now in use. From this Version on ,customers need a new activation code.
5.39	000171	v5 Software Packaging	Fixed a bug in the SCCM user kontext.
5.39	000181	v5 Software Packaging	Expanded CreateApp/Package by security scopes.
5.39	000182	v5 Software Packaging	Treon recognizes if there is an app with the same title already in the Create App dialoge and uses the existing app to create a new deployment type.
5.39	000183	v5 Software Packaging	CreateApp/Package is now availible through Windows Management Instrumentation. SQL connection is not required.
5.39	000180	v5 System Operations	Adjusted the filter of the applications in packaging infos: Ist now possible to sort applications by f.e. sysStatus in the operations modul.
5.39	000169	v5 System Operations	The refresh computer function no longer ignores the computer template.
5.32	000156	v5 System Operations	Fixed issue with the addon software (XML error).
5.31	000149	v5 Kernel	Enabled a ‘Read Only’ parameter for the whole formula/workflow/role.
5.31	000150	v5 Kernel	ID columns can be displayed in lists, now.
5.30	000145	v5 Kernel	Text fields are now saved as VarChar (10000) in the database.
5.30	000148	v5 Kernel	Fixed a bug that caused the ‘link’ button to disappear if the displayname reaches a certain length.
5.20.00	000125	v5 Kernel	New variable SiteURL now exists,it can be used to reference on an Email dynamically.
5.20.00	000136	v5 Kernel	Fixed bugs that affected the saving of the Formulardata when using the execute function.
5.20.00	000139	v5 Kernel	The number of connections will now be displayed in the list view.
5.20.00	000074	v5 Software Packaging	The ‘Execute’ Command is not displayed anymore if there is no token.
5.20.00	000121	v5 Software Packaging	The Email function has been upgraded, it is now possible to set Email templates and connect them to Workflows. Emails are sent when the Email Condition is positive.
5.20.00	000124	v5 Software Packaging	SCCM gateway has been extended it now supports AppVDeployment Types.
5.19.00	000098	v5 Rollout Center	Adjusted import export dialog.
5.19.00	000076	v5 Rollout Center	The Connections icon is now correctly displayed.
5.19.00	000072	v5 Rollout Center	Fixed a bug that caused a ‘LoadXML Error’ when trying to add an active directory user to a list view.
5.19.00	000077	v5 Software Packaging	Applications get created automatically within a Folder structure, as in packages.
5.19.00	000101	v5 Software Packaging	PackWF/RolloutDB formular now got differentiated CSS classes.
5.19.00	000068	v5 System Operations	Computer refresh applications (‘packages’) is not displaying updates (and task sequences) as requested.
5.18.00	000073	v5 Kernel	Fixed a bug which caused an empty window to be displayed, when the Website wasnt used for a certain time because of a timeout of the Internet Information Server.
5.18.00	000083	v5 Kernel	Session timeout adjusted to 3 days to prevent Website from displaying a blank page.
5.18.00	000090	v5 Software Packaging	Dynamic paths do work properly again. It is possible to support multiple wrappers via copyjob.
5.18.00	000091	v5 Software Packaging	Changes in the Package System are now working properly again.
5.18.00	000094	v5 Software Packaging	The Create Collection command now supports nested text names for the destination folder. If the folder does not exist it will be created.
5.18.00	000080	v5 Software Packaging	Adjusted formular design.
5.18.00	000069	v5 System Operations	It is now possible to use a GUID to create a new Client in the system.

Supported Configurations¶

Supported Microsoft SQL Server Versions¶

Product	Version	Supported
SQL Server 2008	10.0	Yes
SQL Azure	10.25	Yes
SQL Server 2008 R2	10.5	Yes
SQL Server 2012	11.0	Yes
SQL Server 2014	12.0	Yes
SQL Server 2016	13.0	Yes

Supported Microsoft Windows Server Versions¶

Product	Version	Supported
Windows Server 2008	NT 6.0	Yes
Windows Server 2008 R2	NT 6.1	Yes
Windows Server 2012	NT 6.2	Yes
Windows Server 2012 R2	NT 6.3	Yes
Windows Server 2016	NT 10.0	Yes

Supported .Net Framework Versions¶

Hence the code was written in .Net 2.0 only this version is supported.

Supported Microsoft ConfigMgr Versions¶

Product	Revision	Service Pack	Version/Build	Supported
Systems Management Server (SMS)	1.0			No
Systems Management Server (SMS)	1.1			No
Systems Management Server (SMS)	1.2			No
Systems Management Server (SMS)	2.0			No
Systems Management Server (SMS)	2003			No
Systems Management Server (SMS)	2003 R2			No
System Center Configuration Manager (ConfigMgr)	2007	Beta 1	4.00.5135.0000	No
System Center Configuration Manager (ConfigMgr)	2007	RTM	4.00.5931.0000	Yes
System Center Configuration Manager (ConfigMgr)	2007	SP1	4.00.6221.1000	Yes
System Center Configuration Manager (ConfigMgr)	2007	SP1	4.00.6221.1193	Yes
System Center Configuration Manager (ConfigMgr)	2007	SP2	4.00.6487.2000	Yes
System Center Configuration Manager (ConfigMgr)	2007	SP2	4.00.6487.2111	Yes
System Center Configuration Manager (ConfigMgr)	2007		4.00.6487.2157	Yes
System Center 2012 Configuration Manager (ConfigMgr)	2012	Beta 1		No
System Center 2012 Configuration Manager (ConfigMgr)	2012	Beta 2	5.00.7561.0000	No
System Center 2012 Configuration Manager (ConfigMgr)	2012	Release Candidate 1	5.00.7678.0000	No
System Center 2012 Configuration Manager (ConfigMgr)	2012	Release Candidate 2	5.00.7703.0000	No
System Center 2012 Configuration Manager (ConfigMgr)	2012	RTM	5.00.7711.0000	Yes
System Center 2012 Configuration Manager (ConfigMgr)	2012	Cumulative Update 1	5.00.7703.0200[5]	Yes
System Center 2012 Configuration Manager (ConfigMgr)	2012	SP1 Beta	5.00.7782.1000[6]	No
System Center 2012 Configuration Manager (ConfigMgr)	2012	SP1	5.00.7804.1000	Yes
System Center 2012 Configuration Manager (ConfigMgr)	2012 R2	R2	5.00.7958.1000	Yes
Configuration Manager			1511	Yes
Configuration Manager			1602	Yes

Note

In regard to support for the new Configuration Manager versions (beginning from Build 1511): Silver Monkey’s release cycle is based on the release cycles of Microsoft. 4 weeks after publication of a new build version it is supported by Silver Monkey.

Support¶

If you have further questions regarding out products or the documentation contact us:

Tel. : +49 40 - 226 383 160
E-Mail : Support@SilverMonkey.net

If you need general Information about our Products visit: http://www.SilverMonkey.net