﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server Newbies  / powershelling against cms - problems in test / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 19 Jun 2013 17:35:30 GMT</lastBuildDate><ttl>20</ttl><item><title>powershelling against cms - problems in test</title><link>http://www.sqlservercentral.com/Forums/Topic1430956-1292-1.aspx</link><description>Hi All - I'm a new DBA.  Trying to create a sql job that evaluates policies against our cms.  I have it working locally going against our test cms.  When I move the job up to a test server, the first step of the job bombs on the first line of the powershell script:--Error MessageThe corresponding line is 'import-module sqlps -DisableNameChecking'. Correct the script and reschedule the job. The error information returned by PowerShell is: 'The term 'import-module' is not recognized as the name of a cmdlet, function, script file, or operable program.--I am using a proxy for this step and I have researched it trying several different solutions.  Any suggestions or hints on how to get sqlps imported successfully within a powershell job step?  I cannot run scripts from steps, so that is out.Thanks in advance.</description><pubDate>Thu, 14 Mar 2013 07:28:47 GMT</pubDate><dc:creator>random_name</dc:creator></item></channel></rss>