smlets Issue Tracker Rss Feed

Created Issue: Get-SMProperty PowerShell 3 Incompatibility [10983]

da7rutrak — Tue, 07 May 2013 21:17:14 GMT

When trying to run get-smproperty using Powershell 3, One will receive an error similar to the following:

```
add-member : Cannot add a member with the name "Class" because a member with that name already
exists. If you want to overwrite the member anyway, use the Force parameter to overwrite it.
At line:2 char:35
+ $class.GetProperties("recursive")|add-member -pass NoteProperty Class $class |
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (SRText1:PSObject) [Add-Member], InvalidOperation
Exception
+ FullyQualifiedErrorId : MemberAlreadyExists,Microsoft.PowerShell.Commands.AddMemberCommand
```

Repro steps:

1. Open Powershell V3
2. Import SMlets module
3. Run : get-smproperty -classname [classname guid from XML or SCSMAuthoring Tool]

Workaround:
1. Open powershell v2 (start > run > powershell -v 2)
2. Run commands as normal.

Commented Issue: Incident Title is not being set property in New-SCSMIncident [8942]

radtravis — Wed, 27 Feb 2013 18:22:35 GMT

if you create a new incident using New-SCSMIncident the title is not searchable when the incident is created.

The work around is to manually go in to the ticket and click OK. At that point the ticket title is searchable using the standard console functionality
Comments: ** Comment from web user: radtravis **

We need to set the .DisplayString property to be equal to String.Format({0}{1} - {2}, strIncidnetIDPrefix, {0}, strTitle).

Closed Issue: Trouble with object types returned using SMlets [10670]

radtravis — Wed, 27 Feb 2013 18:18:30 GMT

I am trying to use set-scsmobjecttemplate$CMN11 = Get-SCSMObjectTemplate -DisplayName "CMN11 - Request for Results Notification"$CRClassProjection = get-SCSMTypeProjection System.WorkItem.ChangeRequestProjection$$CRP = Get-SCSMObjectProjection -Projection $CRClassProjection -Filter "Id -eq $CR_ID"Set-SCSMObjectTemplate -Projection $CRP -Template $CMN11PS C:\>>> Set-SCSMObjectTemplate -Projection $CRP -Template $CMN11Set-SCSMObjectTemplate : The template cannot be applied to the instance because the instance is not of the template targets type.At line:1 char:23+ Set-SCSMObjectTemplate <<<< -Projection $CRP -Template $CMN11 + CategoryInfo : InvalidOperation: (Template_ae893e...2e7f27753abdbe3:ManagementPackObject Template) [Set-SCSMObjectTemplate], InvalidOperationException + FullyQualifiedErrorId : ApplyTemplate,SMLets.SetSCSMObjectTemplateCommand And I think this is the cause, PS C:\>>> $CRP = Get-SCSMObjectProjection -Projection $CRClassProjection -Filter "Id -eq $CR_ID"PS C:\>>> $CRP.GetType()IsPublic IsSerial Name BaseType-------- -------- ---- --------True False PSCustomObject System.Object PS C:\>>> $CRClassProjection.GetType()IsPublic IsSerial Name BaseType-------- -------- ---- --------True False PSCustomObject System.ObjectAnd according to the cmdlet help, we are looking for a specific type of object, PS C:\>>> help Set-SCSMObjectTemplateNAME Set-SCSMObjectTemplateSYNTAX Set-SCSMObjectTemplate [-Projection] [-Name ] [-Tem plate ] [-ComputerName ] [-Credential ] [-SCSMSe ssion ] [-Verbose] [-Debug] [-ErrorAction ] [-WarningAc tion ] [-ErrorVariable ] [-WarningVariable ] [-OutVariable ] [-OutBuffer ] [-WhatIf] [-Confirm] Set-SCSMObjectTemplate [-Object] [-Name ] [-Template ] [-ComputerName ] [-Credential ] [-SCSMSession ] [-Verbose] [-Debug] [-ErrorAction ] [-WarningAction ] [-ErrorVariable ] [-WarningVariable ] [-OutVariable ] [-OutBuffer ] [-WhatIf] [-Confirm]
Comments: Incorrect usage of cmdlet

Commented Issue: Unable to import module after upgrading to SCSM 2012 SP1 [10764]

radtravis — Wed, 27 Feb 2013 18:16:15 GMT

After upgrading to SCSM 2012 SP1, the following exception is thrown when attempting to import the SMlets module. I suspect they will need a recompile against the the SP1 bits.

Command execution stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot load Windows PowerShell snap-in C:\Program Files\Common Files\SMLets\SMLets.Module.dll because of the following error: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Loader Exceptions:

Could not load file or assembly 'Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Could not load file or assembly 'Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Could not load file or assembly 'Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Comments: ** Comment from web user: radtravis **

I am able to use SMLets Beta 4 with SCSM 2012 SP1 without any errors. I did a clean install of SCSM though not an upgrade from SCSM 2012. Can you please try uninstalling and reinstalling SMLets?

Created Issue: -UserComment switch for Set-SCSMIncident is not documented [10770]

kmongwa — Thu, 24 Jan 2013 14:09:54 GMT

-UserComment switch for Set-SCSMIncident (original work item 7118) is not document in usage syntax. Please add it to usage syntax so it is easily discoverable

Created Issue: Unable to import module after upgrading to SCSM 2012 SP1 [10764]

zaepho — Mon, 21 Jan 2013 23:13:30 GMT

Commented Issue: System.Exception: The specified snap-in 'SMlets' failed to load [10705]

JFadmin — Fri, 28 Dec 2012 01:29:28 GMT

System.Exception: The specified snap-in 'SMlets' failed to load with below exception

System.Management.Automation.PSArgumentException: No snap-ins have been registered for Windows PowerShell version 2.

I have created several powershell scripts that run fine with I run them on the server, however, when I package them in the SM Authoring tool, and deploy them (import MP & copy DLLs) they fail to load the SMlets module.

I believe I have beta3 installed. (how do I check?)

This is SCSM 2012 - on all x64 server Windows 2008 R2

I was initially trying to have the module load via the GUI option in the Authoring tool, then i tried to remove that, and add the import and removal directly in the script.

But is keeps faling with that error... I have only installed SMlets on the management server, not the DW... (do I need to?)

Here is a simple script that fails.
$a = (get-module|%{$_.name}) -join " "
if(!$a.Contains("SMLets")){Import-Module SMLets -ErrorVariable err -Force}

$CRClass = get-scsmclass -name System.WorkItem.ChangeRequest$
$CRobj = Get-SCSMObject -Class $CRClass -Filter "ID -eq $CRID"

if ($CRobj.Status.displayname -eq "approved")
{
$i = 0
if ($CRobj.ActualStartDate -ne $null) {$i++}
if ($CRobj.ActualEndDate -ne $null) {$i++}
if ($CRobj.ImplementationResults -ne $null) {$i++}
}

if ($i -eq 3){Set-SCSMObject -SMObject $CRobj -Property status -Value "executed"}

Remove-module smlets -force
Comments: ** Comment from web user: JFadmin **

I was able to fix this by calling the SMlets module with the literal Path.

$a = (get-module|%{$_.name}) -join " "
if(!$a.Contains("SMLets")){Import-Module 'C:\Program Files\Common Files\SMLets\SMLets.psd1' -ErrorVariable err -Force}

Created Issue: System.Exception: The specified snap-in 'SMlets' failed to load [10705]

JFadmin — Fri, 28 Dec 2012 00:15:52 GMT

Commented Issue: Trouble with object types returned using SMlets [10670]

JFadmin — Fri, 28 Dec 2012 00:06:08 GMT

I am trying to use set-scsmobjecttemplate $CMN11 = Get-SCSMObjectTemplate -DisplayName "CMN11 - Request for Results Notification" $CRClassProjection = get-SCSMTypeProjection System.WorkItem.ChangeRequestProjection$ $CRP = Get-SCSMObjectProjection -Projection $CRClassProjection -Filter "Id -eq $CR_ID" Set-SCSMObjectTemplate -Projection $CRP -Template $CMN11 PS C:\>>> Set-SCSMObjectTemplate -Projection $CRP -Template $CMN11 Set-SCSMObjectTemplate : The template cannot be applied to the instance because the instance is not of t he template targets type. At line:1 char:23 + Set-SCSMObjectTemplate <<<< -Projection $CRP -Template $CMN11 + CategoryInfo : InvalidOperation: (Template_ae893e...2e7f27753abdbe3:ManagementPackObject Template) [Set-SCSMObjectTemplate], InvalidOperationException + FullyQualifiedErrorId : ApplyTemplate,SMLets.SetSCSMObjectTemplateCommand And I think this is the cause, PS C:\>>> $CRP = Get-SCSMObjectProjection -Projection $CRClassProjection -Filter "Id -eq $CR _ID" PS C:\>>> $CRP.GetType() IsPublic IsSerial Name BaseType -------- -------- ---- -------- True False PSCustomObject System.Object PS C:\>>> $CRClassProjection.GetType() IsPublic IsSerial Name BaseType -------- -------- ---- -------- True False PSCustomObject System.Object And according to the cmdlet help, we are looking for a specific type of object, PS C:\>>> help Set-SCSMObjectTemplate NAME Set-SCSMObjectTemplate SYNTAX Set-SCSMObjectTemplate [-Projection] [-Name ] [-Tem plate ] [-ComputerName ] [-Credential ] [-SCSMSe ssion ] [-Verbose] [-Debug] [-ErrorAction ] [-WarningAc tion ] [-ErrorVariable ] [-WarningVariable ] [-OutVariable ] [-OutBuffer ] [-WhatIf] [-Confirm] Set-SCSMObjectTemplate [-Object] [-Name ] [-Template ] [-ComputerName ] [-Credential ] [-SCSMSession ] [-Verbose] [-Debug] [-ErrorAction ] [-WarningAction ] [-ErrorVariable ] [-WarningVariable ] [-OutVariable ] [-OutBuffer ] [-WhatIf] [-Confirm]
Comments: ** Comment from web user: JFadmin **

I found that I was attempting to use this cmdlet incorrectly. I was trying to apply an email notification template.

Created Issue: Trouble with object types returned using SMlets [10670]

JFadmin — Mon, 17 Dec 2012 14:19:27 GMT

I am trying to use set-scsmobjecttemplate

$CMN11 = Get-SCSMObjectTemplate -DisplayName "CMN11 - Request for Results Notification"
$CRClassProjection = get-SCSMTypeProjection System.WorkItem.ChangeRequestProjection$
$CRP = Get-SCSMObjectProjection -Projection $CRClassProjection -Filter "Id -eq $CR_ID"
Set-SCSMObjectTemplate -Projection $CRP -Template $CMN11

PS C:\>>> Set-SCSMObjectTemplate -Projection $CRP -Template $CMN11
Set-SCSMObjectTemplate : The template cannot be applied to the instance because the instance is not of t
he template targets type.
At line:1 char:23
+ Set-SCSMObjectTemplate <<<< -Projection $CRP -Template $CMN11
+ CategoryInfo : InvalidOperation: (Template_ae893e...2e7f27753abdbe3:ManagementPackObject
Template) [Set-SCSMObjectTemplate], InvalidOperationException
+ FullyQualifiedErrorId : ApplyTemplate,SMLets.SetSCSMObjectTemplateCommand
And I think this is the cause,
PS C:\>>> $CRP = Get-SCSMObjectProjection -Projection $CRClassProjection -Filter "Id -eq $CR
_ID"
PS C:\>>> $CRP.GetType()

IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True False PSCustomObject System.Object

PS C:\>>> $CRClassProjection.GetType()

IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True False PSCustomObject System.Object

And according to the cmdlet help, we are looking for a specific type of object,
PS C:\>>> help Set-SCSMObjectTemplate

NAME
Set-SCSMObjectTemplate

SYNTAX
Set-SCSMObjectTemplate [-Projection] [-Name ] [-Tem
plate ] [-ComputerName ] [-Credential ] [-SCSMSe
ssion ] [-Verbose] [-Debug] [-ErrorAction ] [-WarningAc
tion ] [-ErrorVariable ] [-WarningVariable ] [-OutVariable ] [-OutBuffer ] [-WhatIf] [-Confirm]
Set-SCSMObjectTemplate [-Object] [-Name ] [-Template ] [-ComputerName ] [-Credential ] [-SCSMSession ] [-Verbose] [-Debug] [-ErrorAction ] [-WarningAction ] [-ErrorVariable ] [-WarningVariable ] [-OutVariable ] [-OutBuffer
] [-WhatIf] [-Confirm]

Commented Issue: Incident Priority is not being set in New-SCSMIncident [8943]

radtravis — Fri, 24 Aug 2012 22:18:38 GMT

The .Priority field is not being set dependent on the urgency and impact.
Comments: ** Comment from web user: radtravis **

A workflow should pick up the incident after it is created and set the priority correctly.

I agree though that ideally New-SCSMIncident should calculate and set the priority correctly on insert. Will consider for a future release.

Created Issue: Cannot create Service Request using Request Offering that doesn't have questsions. [10317]

smithbj — Mon, 09 Jul 2012 23:29:57 GMT

I have a generic Service Request Offering with no questions that is used for one-off requests. When I try to script the creation of the Service Request, I get an error "Object reference not set to the instance of an object". If I use an Offering with Questions, it works fine.

Commented Issue: Issues invoking SMlets from a remote machine [10188]

smithbj — Mon, 11 Jun 2012 23:28:51 GMT

I have SCSM installed in a lab, on a member server. I'm on a laptop that sits outside the domain. I have SMlets installed there too, as well as the authoring toolkit and the SCSM console.

When I try to load the SMlets, the first time I was getting errors because they couldn't find the SDK Binaries folder in the SCSM install folder. These do not seem to be installed with the authoring toolkit nor with the SCSM console. I had to copy them over from the server. It would be useful if the SMlets checked for this and reported an appropriate error, telling users what to do.

Next, once they were loaded, I can invoke them with simple calls, such as Get-SCSMIncident. When I do that however, since SCSM isn't installed locally, I get an unhelpful error:

Get-SCSMIncident : The Data Access service is either not running or not yet initialized. Check the event log for more i
nformation.
At line:1 char:17
+ get-scsmincident <<<<
+ CategoryInfo : InvalidOperation: (localhost:String) [Get-SCSMIncident], ServiceNotRunningException
+ FullyQualifiedErrorId : GenericMessage,SMLets.SCSMIncidentGet

This should be designed better so that the cmdlets check to see if SCSM is installed on the local machine if they're run locally (it could check once and cache it, because it does the check on import), and then if you invoke a local command by accident it should tell you SCSM isn't installed on the local machine.

Also, it would be quite useful to add a Connect-SCSMServer cmdlet, where I could specify the server name and the credentials, and then from that point on every other SMLet I would call would use that connection. That would be much, much easier for remote management of SCSM.
Comments: ** Comment from web user: smithbj **

Try running the script below prior to any cmlets. It should use the computer specified in all scripts you run in that session.

$smdefaultcomputer = 'smserver.domain.local'

Created Issue: Issues invoking SMlets from a remote machine [10188]

poshoholic — Fri, 18 May 2012 22:25:59 GMT

Created Issue: The Credential parameter needs to accept string input as well as PSCredential [10187]

poshoholic — Fri, 18 May 2012 22:20:32 GMT

Today the Credential parameter is implemented inconsistently in these cmdlets. In core PowerShell, you can pass in a string and it will automatically convert to PSCredential using a type converter, which results in a prompt being displayed as if you had called Get-Credential. The SMlets don't do this however, so you must explicitly use Get-Credential, which should not be necessary.

For example, I should be able to do this:

Get-SCSMIncident -ComputerName scsm -Credential SCLab\Administrator

But I cannot. I have to do this instead:

Get-SCSMIncident -ComputerName scsm -Credential (Get-Credential SCLab\Administrator)

Please fix this so that it's consistent with the rest of PowerShell.

Closed Issue: Get-SCSMRelationshipObject ignore -Relationship parameter then QueryBy.Relationship used with filter [9116]

jtruher — Tue, 17 Apr 2012 00:22:34 GMT

Get-SCSMRelationshipObject ignore filter then QueryBy.Relationship used.
Example:
PS C:\Users\gricenko.eng> import-module SMLets
PS C:\Users\gricenko.eng> $rel = Get-SCSMRelationshipClass -Name "System.UserManagesUser"
PS C:\Users\gricenko.eng> Get-SCSMRelationshipObject -Relationship $rel -verbose
VERBOSE: Retrieving Relationship Objects. QueryBy is:Relationship
VERBOSE: Relationship via r: 4a807c65-6a1f-15b2-bdf3-e967e58c254a. Count = 7
VERBOSE: ID: 901a128e-19e5-6e90-a2e8-1cab3b89e3bb
VERBOSE: ID: 349457f9-8228-6938-fc69-298d757f3db9
VERBOSE: ID: edf86c8d-fa6d-df17-6ba4-39d726b379d6
VERBOSE: ID: 91141b3b-a279-5d7b-4a22-4270c806364c
VERBOSE: ID: 18b7b34b-de1a-1548-d72b-497d7f32739d
VERBOSE: ID: 88dd2378-191b-4873-a2a4-79e45d016387
VERBOSE: ID: 2a2087c8-6c83-dd79-60e9-fce0a1f07ead

PS C:\Users\gricenko.eng> Get-SCSMRelationshipObject $rel -Filter "SourceObjectName = 'SYSCENTER.gricenko'" -verbose
VERBOSE: Retrieving Relationship Objects. QueryBy is:Relationship
VERBOSE: Using Filter: SourceObjectName = 'SYSCENTER.gricenko'
VERBOSE: After property name substitution: SourceObjectName = 'SYSCENTER.gricenko'
VERBOSE: Converted filter is: SourceObjectName = 'SYSCENTER.gricenko'
VERBOSE: Relationship with criteria
VERBOSE: ID: abdc9777-468f-2d63-6de1-07edfd94ffa1
VERBOSE: ID: 5ecd152a-5b05-5f6c-4337-09215eaaedbb
VERBOSE: ID: 89bc5c95-6db9-9f1f-8142-0af552fb418d
VERBOSE: ID: f340daef-4d57-15b8-cd02-0b61e91e7ed7
VERBOSE: ID: e97823c5-b2ca-59fc-beab-0cef7c197727
VERBOSE: ID: 06a53af5-3f55-9294-3b59-0d1a28e3cfd0
VERBOSE: ID: 58638ed9-a21e-6eb4-a4fa-0e71bc34659b
VERBOSE: ID: bcbd195b-56a5-e522-d82d-0e9addf11612
VERBOSE: ID: 41a37a00-ec05-306e-fa8f-0ea95f504b52
VERBOSE: ID: 775fe94e-eb3c-ae07-ebb3-102d0a8e28ff
VERBOSE: ID: a118472c-3464-b09b-5869-10a7af81a919
VERBOSE: ID: 82c05367-c774-031b-16be-112881a61e50
VERBOSE: ID: 4d8873a5-f8b6-b5cd-5265-13842a19864f
VERBOSE: ID: a3328916-5d29-ac7f-989b-13a2ad5e469f
VERBOSE: ID: c73667f4-bfd9-84b1-ff99-164b2375685c
VERBOSE: ID: 2a697756-a748-5c4b-0555-1a4397cddc00
VERBOSE: ID: 901a128e-19e5-6e90-a2e8-1cab3b89e3bb
VERBOSE: ID: 3d054009-ecd6-8887-7c71-1e2f53e3ec6a
VERBOSE: ID: 163777b9-45ee-afb0-914b-1e73a865d72a
VERBOSE: ID: bd842434-e137-26c5-baec-20a60f261856
VERBOSE: ID: b727a27d-887a-37f9-d993-21f721c14d07
VERBOSE: ID: 95101748-25a2-2be9-93c2-230e3850ce21
VERBOSE: ID: 54f9dd3b-d95f-6c18-97d6-245c9c4cd65d
VERBOSE: ID: 5982b63d-b208-50d3-1bd6-26f16276ae05
VERBOSE: ID: e364cae3-6d60-34cd-f89e-2808e5d2bd38
VERBOSE: ID: 4c266270-ca10-dc45-42e4-287a9d59603c
VERBOSE: ID: 61103b53-64ef-f8e8-72ef-29e0e8800801
VERBOSE: ID: bd54602b-081c-c0af-0390-2cb7fa57e376
VERBOSE: ID: d6dd23a6-87ec-3494-cf98-2cf42942d9c6
VERBOSE: ID: 64039886-c32f-4c1b-ecf8-303070b17d0f
VERBOSE: ID: c1541a00-ccc3-7c69-15d5-305f51dba1be
VERBOSE: ID: 8fd09bc2-40c4-b395-f661-30ec1618a15c
VERBOSE: ID: e67bd3f6-5e88-e696-a9c4-32ab5b8eeb2f
VERBOSE: ID: edf86c8d-fa6d-df17-6ba4-39d726b379d6
VERBOSE: ID: cb1f3485-5aa0-f978-34be-3e7ba6dee19e
VERBOSE: ID: 3433fdef-b895-3f45-d0c2-3efd4ce462e4
VERBOSE: ID: 2a918149-4375-e815-960c-3fd35c616cab
VERBOSE: ID: dd46ba42-f98d-7ca3-a98d-40edce1d71fc
VERBOSE: ID: 07a6dba4-9385-c8d0-32e8-41fbc19d1ca6
VERBOSE: ID: 46cb30f1-62fc-206d-868b-44078b1b6cbb
VERBOSE: ID: ae0df825-a58d-5636-69c0-45a69771e815
VERBOSE: ID: e9100b0b-2030-6b04-2aed-45fa390065de
VERBOSE: ID: f8c009b4-59f1-e852-991b-46a424b99823
VERBOSE: ID: 7b030266-2d4f-dbdf-17ba-4947cfe427fd
VERBOSE: ID: dc0d2bdc-5b1c-2942-13fe-4ceaf3ed3068
VERBOSE: ID: 93c0160c-8d36-37f5-9606-4cf2d369ba81
VERBOSE: ID: ba4e7a14-af9b-8a1e-a3db-50255d561fbe
VERBOSE: ID: 3c69cd34-2051-f56e-1888-579b06b16c7f
VERBOSE: ID: 538e5e04-5d36-5742-4a66-57f0792bdf09
VERBOSE: ID: a477e020-a09b-b6dc-1ac7-593fda5990d3
VERBOSE: ID: 0a4953cd-4478-528f-028f-5972248b4cc1
VERBOSE: ID: 82e38ac8-5422-f653-1db3-598a691c571a
VERBOSE: ID: 78280ab5-be50-5cf7-4c70-5b14ea49b984
Comments:

Closed Issue: Get-SCSMIncident and Set-SCSMIncident on SCSM 2012 Beta [9671]

jtruher — Tue, 17 Apr 2012 00:22:05 GMT

Hi,

Get-SCSMIncident and Set-SCSMIncident don’t work, with any criteria, on SCSM 2012 Beta, I get the following error:

Get-SCSMIncident : The criteria could not be parsed. See inner exception for details.
At line:1 char:17
+ Get-SCSMIncident <<<< -ID ir4679
+ CategoryInfo : NotSpecified: (:) [Get-SCSMIncident], InvalidCriteriaException
+ FullyQualifiedErrorId : Microsoft.EnterpriseManagement.Common.InvalidCriteriaException,SMLets.SCSMIncidentGet

Get-SCSMObject and Set-SCSMObject cmdlets can be used for many scenrarios.

However, I’ve to attach file(s) to an existing incident (Set-SCSMIncident –Id IRxx –AttachmentPath “xxx”), and I've no quick solution.

Thanks
Best regards
Thierry
Comments:

fixed in beta 4

Closed Issue: Enumeration field not being updated with Set-SCSMObject [9403]

jtruher — Tue, 17 Apr 2012 00:21:40 GMT

Hi, I'm testing the latest version (beta 3). When I want to update an enumeration field it doesn't fail, but it's not updating the field.

Is there something wrong that I'm missing?

PS C:\> $inc

ClassName DisplayName LastModified
--------- ----------- ------------
System.WorkItem.Incident IR93218 - Enterprise Systems - Daily Metrics... 10/25/2011 11:20:11 AM

PS C:\> $inc.Classification

ordinal name displayname
------- ---- -----------
40 IncidentClassificationEnum.Other Other

PS C:\> $IncidentClassif

ordinal name displayname
------- ---- -----------
12.5 Enum.379e4ebc9d8c46f0b33e9307c697cfe4 Database

PS C:\> $inc |Set-SCSMObject -Property Classification -Value $IncidentClassif -ComputerName $MS -verbose
VERBOSE: Want to set Classification(enum) to Enum.379e4ebc9d8c46f0b33e9307c697cfe4
VERBOSE: Looking Enum via string Enum.379e4ebc9d8c46f0b33e9307c697cfe4 in IncidentClassificationEnum
VERBOSE: found enum: Enum.379e4ebc9d8c46f0b33e9307c697cfe4
VERBOSE: set the value
VERBOSE: Adding 4f8d41bd-1b47-0f0b-c468-3e3aece592ed to change list
VERBOSE: Performing operation "Set-SCSMObject" on Target "SMObjects".

PS C:\> $inc = Get-SCSMObject -Class $IncidentClass -Filter "ID -eq IR93218" -ComputerName $MS
PS C:\> $inc.Classification

ordinal name displayname
------- ---- -----------
40 IncidentClassificationEnum.Other Other

PS C:\> $IncidentClassifId = $IncidentClassif.Id

PS C:\> $inc |Set-SCSMObject -Property Classification -Value $IncidentClassifId -ComputerName $MS -verbose
VERBOSE: Want to set Classification(enum) to 5db4ea14-8e93-8e47-f50d-2ad3d05e62ea
VERBOSE: Looking Enum via string 5db4ea14-8e93-8e47-f50d-2ad3d05e62ea in IncidentClassificationEnum
VERBOSE: found enum: Enum.379e4ebc9d8c46f0b33e9307c697cfe4
VERBOSE: set the value
VERBOSE: Adding 4f8d41bd-1b47-0f0b-c468-3e3aece592ed to change list
VERBOSE: Performing operation "Set-SCSMObject" on Target "SMObjects".

PS C:\> $inc = Get-SCSMObject -Class $IncidentClass -Filter "ID -eq IR93218" -ComputerName $MS
PS C:\> $inc.Classification

ordinal name displayname
------- ---- -----------
40 IncidentClassificationEnum.Other Other

PS C:\> $inc |Set-SCSMObject -ComputerName $MS -PropertyHashtable @{Classification = $IncidentClassifId} -verbose
VERBOSE: Want to set Classification(enum) to 5db4ea14-8e93-8e47-f50d-2ad3d05e62ea
VERBOSE: Looking Enum via string 5db4ea14-8e93-8e47-f50d-2ad3d05e62ea in IncidentClassificationEnum
VERBOSE: found enum: Enum.379e4ebc9d8c46f0b33e9307c697cfe4
VERBOSE: set the value
VERBOSE: Adding 4f8d41bd-1b47-0f0b-c468-3e3aece592ed to change list
VERBOSE: Performing operation "Set-SCSMObject" on Target "SMObjects".

PS C:\> $inc = Get-SCSMObject -Class $IncidentClass -Filter "ID -eq IR93218" -ComputerName $MS
PS C:\> $inc.Classification

ordinal name displayname
------- ---- -----------
40 IncidentClassificationEnum.Other Other

Thanks!
Comments:

Closed Issue: can't install msi-package [9310]

jtruher — Tue, 17 Apr 2012 00:21:06 GMT

Trying to install the msi - getting the next
"Этот установочный пакет не поддерживается этим типом процессора. Обратитесь за помощью к поставщику продукта."
In English
"This installation package is not supported by this processor type..."
I'm running w7prof sp1, 32bit, Intel(R) Core(TM)2 Quad CPU Q8400 © 2.66GHz 2.66 GHz
Comments:

fixed

Closed Issue: The SMLets should not be installing into $PSHome\Modules! [9724]

jtruher — Tue, 17 Apr 2012 00:20:36 GMT

$PSHome is defined as Windows\System32\WindowsPowerShell\v1.0\Modules. This folder is used for modules that ship with PowerShell or as part of the operating system that includes PowerShell. Other products should not be installing modules into that location.

Today the SMLets are installed into this folder. That should be changed such that the SMLets install into a Program Files folder and such that the SMLets installer modifies the PSModulePath environment variable to include the path to that module using the %ProgramFiles% environment variable if the path is not already present. This way the module is discoverable on all systems and to all users without adding files to the Windows folder hierarchy.
Comments:

fixed in beta4