Quantcast
Channel: SCSM PowerShell Cmdlets
Viewing all 306 articles
Browse latest View live
↧

New Post: Apply template to new incident based on keywords

April 9, 2012, 1:52 pm
$
0
0

I am looking to see if it's possible to apply a template based on words found in the title or description and apply a template to it. The powershell script would run every 30 seconds or so and based on a list or text file be able to apply a specific template setup in my enviroment.

This is my scenario -

1. User send e-mail to support e-mail address to create an incident.

2. System creates incident....based on keywords it applies a template such as MIS Support template, etc. (Template is setup with the settings to set off a subscription e-mail based on the supportgroup change)

3. The subscription which I have created looks to see if the support group field has changed from does not equal mis support queue to does equal mis support queue. This way it will send an e-mail notification to the recipients in the queue(ad group). I have tested the subscription works when I manually apply a template. The users get an e-mail notifying them that the incident has been assigned to the queue.

I am no powershell expert or novice so if you can point me to the articles that can help I will learn to create something that will work..I hope. Any suggestions would be appreciated.

Thanks

↧
Search

Closed Issue: can't install smlets Beta 3 on Win7 32bit [9883]

April 16, 2012, 5:19 pm
$
0
0
I downloaded the SMLets to install on Win7 32bit and it gives me the error "..This installation package is not supported by this processor type..." and I don't understand what you said about "retrieve from wix directory"... sorry I am not familiar with the MSI technology. can you please give me some more instruction? thanks!
Comments:

fixed in beta 4

↧
↧

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

April 16, 2012, 5:20 pm
$
0
0
$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

↧

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

April 16, 2012, 5:21 pm
$
0
0
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: Enumeration field not being updated with Set-SCSMObject [9403]

April 16, 2012, 5:21 pm
$
0
0
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: Get-SCSMIncident and Set-SCSMIncident on SCSM 2012 Beta [9671]

April 16, 2012, 5:22 pm
$
0
0
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: Get-SCSMRelationshipObject ignore -Relationship parameter then QueryBy.Relationship used with filter [9116]

April 16, 2012, 5:22 pm
$
0
0
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:

↧

New Post: Affected user is not anymore an employee

April 21, 2012, 9:23 pm
$
0
0

Hello guys...I'm really new on this, but I'm learning fast ;) I hope you can help me..I have this situation...

There are several Active incidents related to users that are not longer company employees. So basically the idea is to run an ps script including as a parameter the Incident Affected User so all the ACTIVE and RESOLVED related incidents will be automatically changed to closed.

I was exploring and trying something like this...but I bealive is not optimized...and probably is not sure to put into a production envirnonment. 

get-scsmtypeprojection System.WorkItem.Incident.ProjectionType|Get-SCSMObjectProjection|?{$_.AffectedUser -like '*George Bush*'}|%{$_.object}|set-SCSMIncident -Status Closed

Problems:

*I cant find the way to replace the -like for some to expres equal doing a faster query and a correct match

*I cant add the Status to avoid include already Closed incident in the object protection filters

*finally, the performance I'm getting is really bad...and I have only 5000 incidents in my test db.

Thanks - Gus

↧
Search

New Post: Affected user is not anymore an employee

April 24, 2012, 11:34 pm
$
0
0

first, you should use a different projection. The System.WorkItem.Incident.ProjectionType carries a lot more than you need, and with all those additional relationships, the amount of data that will be returned could be massive. You also need the script I wrote some time ago for building a projection criteria which didn't seem to make it into the smlets module (http://jtruher3.wordpress.com/2011/05/13/retrieving-projection-data-with-criteria/). You'll need to save that script and use it:

here's an example:

 

PS# $projection = get-scsmtypeprojection System.WorkItem.Incident.View.ProjectionType|select -first 1
PS# $projection

ProjectionType: System.WorkItem.Incident.View.ProjectionType
ProjectionSeed: System.WorkItem.Incident
Components:
   Alias                          TargetType         TargetEndPoint
   -----                          ----------         ---------------
   AffectedUser                   System.User        RequestedWorkItem
   AssignedUser                   System.User        AssignedWorkItem


PS# get-scsmobjectprojection -Projection $projection

Id          Title                                           AssignedTo        Status  Priority AffectedUser         LastModified
--          -----                                           ----------        ------  -------- ------------         ------------
CustomIR276 Nihil iriure sanctus gubergren invidunt commodo Luptatum Sanctus  Closed         2 Id Amet              3/24/2012 11:14:23 PM
CustomIR274 At laoreet vulputate voluptua vel accumsan      Velit Sea         Pending        9 Vero Enim            3/24/2012 11:14:23 PM
CustomIR277 Aliquam invidunt stet nonumy dolores duo        Velit Sea         Pending        1 Id Amet              3/24/2012 11:14:23 PM
CustomIR279 Voluptua gubergren eos in accusam elitr         Invidunt Sea      Active         1 Stet Sit             3/24/2012 11:14:23 PM
CustomIR273 Esse erat facilisis kasd id consequat           Aliquyam Volutpat Closed         6 In Eum               3/24/2012 11:14:23 PM
CustomIR282 Ut rebum gubergren diam diam duo                Stet Sit          Pending        2 Stet Sit             3/24/2012 11:14:23 PM
CustomIR281 Dolor clita voluptua wisi elitr aliquam         Vero Enim         Pending        2 JWT-D4.Administrator 3/24/2012 11:14:23 PM
CustomIR280 Illum ut minim velit no sit                     Accusam Justo     Pending        2 Velit Sea            3/24/2012 11:14:23 PM
CustomIR275 Eos dignissim congue imperdiet dolore ea        In Eum            Active         2 Luptatum Sanctus     3/24/2012 11:14:23 PM
CustomIR278 Clita sed accusam accusam dolor labore          Velit Sea         Closed         3 Invidunt Sea         3/24/2012 11:14:23 PM
PS# $criteria = new-scsmProjectionCriteria.ps1 -projection $projection -filter "AffectedUser.DisplayName -eq 'Stet Sit'"
PS# Get-SCSMObjectProjection -Criteria $criteria
Id          Title                                   AssignedTo   Status  Priority AffectedUser LastModified
--          -----                                   ----------   ------  -------- ------------ ------------
CustomIR279 Voluptua gubergren eos in accusam elitr Invidunt Sea Active         1 Stet Sit     3/24/2012 11:14:23 PM
CustomIR282 Ut rebum gubergren diam diam duo        Stet Sit     Pending        2 Stet Sit     3/24/2012 11:14:23 PM

 

 


 

Then, once you've got to this point, you can set the closed state:

PS# Get-SCSMObjectProjection -Criteria $criteria | %{$_.object}|set-scsmobject -PropertyHashtable @{ Status = "Closed" }
(which sets the status, and below is the proof :^)
PS# Get-SCSMObjectProjection -Criteria $criteria

Id          Title                                   AssignedTo   Status Priority AffectedUser LastModified
--          -----                                   ----------   ------ -------- ------------ ------------
CustomIR279 Voluptua gubergren eos in accusam elitr Invidunt Sea Closed        1 Stet Sit     4/24/2012 11:31:17 PM
CustomIR282 Ut rebum gubergren diam diam duo        Stet Sit     Closed        2 Stet Sit     4/24/2012 11:31:16 PM

Also, you should be able to provide a two part criteria:

$criteria = new-scsmProjectionCriteria -projection $projection -filter "AffectedUser.DisplayName -eq 'Stet Sit' -and Status -ne 'Closed'"

which will further reduce the amount of retrieved data

 

jim

↧
↧

New Post: Affected user is not anymore an employee

April 25, 2012, 3:40 am
$
0
0

Thanks Jim, I'll try it today an let you know. Thank you very much for your time and the help!

Gus

↧

New Post: What shoud be value for -Parent parameter for Add-SCSMEnumeration command

April 29, 2012, 7:08 am
$
0
0

I am adding a new value to an existing dropdown list using a cmlets in powershell , what value should be provided to the -Parent parameter for Add-SCSMEnumeration command.How to retrieve the value which should be provided for -Parent parameter.

I tried providing it EnumTypeName , EnumTypeId, ManagementPackId from EnumType Table , but still it is giving error.

Add-SCSMEnumeration : Cannot bind parameter 'Parent'. Cannot convert the "2374E644-12CF-5AFB-0BD0-C924BFB0E17A" value of
 type "System.String" to type "Microsoft.EnterpriseManagement.Configuration.ManagementPackEnumeration".

↧

New Post: Problem executing Import-Module SMLets

May 7, 2012, 7:35 am
$
0
0

Hello:

I'm running SCSM 2010 SP1 + CU3.

I installed the SMLets, downloaded from CodePlex. This one: Smlets2010SP1-x64.

When I try to execute Import-Module SMLets, this error appears:

Cannot load Windows PowerShell snapin ...\SMLets.Module.dll because of the following error: Unable to load one or more of the requested types.... Could not load file or assembly 'Microsoft.EnterpriseManagement.Core, Version=7.0.500.0...'...The system cannot find the file specied.

Well, I look for the file and mine is version 7.0.6555.128.

What can I do?

Any comment or suggestion would be appreciated. I have a thread here http://social.technet.microsoft.com/Forums/en-US/customization/thread/0525e574-4c97-438c-b409-fada22f729c0

Regards,

Felipe Román http://feliperoman.wordpress.com

↧

New Post: Problem executing Import-Module SMLets

May 7, 2012, 3:56 pm
↧
↧

New Post: how to use new-scqueue?

May 8, 2012, 5:16 am
$
0
0

Hi,

Could anyone give me an example how to use new-scqueue, -QueryOption is what interest me the most.

Regards,

Prem

↧

New Post: how to use new-scqueue?

May 9, 2012, 10:28 am
$
0
0

-QueryOption has no effect on new-scqueue at all (it's an artifact of the base class). If you would like to see an example of use, look in the test folder for test-scqueue, which should get you started.

↧
Search

New Post: how to use new-scqueue?

May 11, 2012, 1:49 am
$
0
0

Thanks Jim,

Yesterday I found an answer in project code comments :)

↧

New Post: What shoud be value for -Parent parameter for Add-SCSMEnumeration command

May 11, 2012, 8:57 am
$
0
0

Here's an example of adding an enum value to the IncidentSourceEnum, notice that you need a MangementPack and the parent enumeration, in this case, I'm using IncidentSourceEnum, but the principle is the same

 

PS> $mp = Get-SCSMManagementPack anmpforEnum
PS> Get-SCSMEnumeration incidentsourceenum$

ordinal name               displayname
------- ----               -----------
        IncidentSourceEnum Incident Source

PS> $parentEnum = Get-SCSMEnumeration incidentsourceenum$
PS> Add-SCSMEnumeration -Parent $parentEnum -ManagementPack $mp `
>> -Name IncidentSourceEnum.AddedEnum `
>> -DisplayName "Additional Incident Source" `
>> -Ordinal 50
PS> get-scsmenumeration incidentsourceenum

ordinal name                         displayname
------- ----                         -----------
20      IncidentSourceEnum.Portal    Portal
0       IncidentSourceEnum.Console   Console
15      IncidentSourceEnum.Phone     Phone
5       IncidentSourceEnum.DCM       Configuration Manager (DCM)
50      IncidentSourceEnum.AddedEnum Additional Incident Source
        IncidentSourceEnum           Incident Source
25      IncidentSourceEnum.SCOM      Operations Manager
30      IncidentSourceEnum.System    System
10      IncidentSourceEnum.Email     E-Mail
↧
↧

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

May 18, 2012, 3:20 pm
$
0
0
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.
↧

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

May 18, 2012, 3:25 pm
$
0
0
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.
↧

New Post: Set First Response Date

May 21, 2012, 6:09 am
$
0
0

Hello - I'm a total beginner when it comes to poweshell, but i need to create a script for a workflow, and i wondered if there was anyone that could give me a starting point...

What i need to achieve is when an incident get's a First Assigned Date the First Response Date gets set to be the same. As for us this is the first moment a job has been picked up by somebody.

Is this pretty simple?

Cheers - Andrew.

↧
Viewing all 306 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>