Hi Ryan, 

just to let you know you can do DetectDeploymentTypeByCustomScript switch and 
ScriptContent & ScriptType for detection methods outside of MSI Deployment 
types we have just used this one, works pretty well with an automated task we 
put in.


Cheers


Steve






From: Ryan
Sent: ‎Thursday‎, ‎10‎ ‎July‎ ‎2014 ‎9‎:‎59‎ ‎AM
To: [email protected]





Ah, gotcha. I think you are going to be able to do most of your job through 
Powershell. You will not be able to do much with Task Sequences, but otherwise 
I think you'll be fine managing collections, devices, applications, 
infrastructure, etc. 



You will run across a few things every now and then that can not be done 
through Powershell. For instance, you can not create detection methods for 
application deployment types other than MSI or script in Powershell. So in 
order to do a file or registry detection method, you would need to do extra 
work to write it in a script. 




I don't use Powershell for my day to day tasks, so there may be a number of 
other things that Powershell is missing. I'd say set up a test environment and 
play around. 













On Wed, Jul 9, 2014 at 2:28 PM, Ryan Shugart <[email protected]> wrote:




Well, to make a really long and complex answer shorter and less complex.  I’m 
blind, and I use a screen reader to navigate windows.  I use keyboard commands 
to get around, and my screen reader reads the focused item.  With the SCCM 2007 
console this worked really well.  The console had its short comings of course, 
but it was really easy to get where I needed and I could read most information. 
 With 2012 it’s a very different story, there are parts I can get to, but 
there’s a lot I can’t get to.  We have tickets open with Microsoft, but they’re 
moving slowly, and I’ve held this upgrade off for as long as I can.  We’re at 
the point were we just have to upgrade things.  So, I’m looking into other ways 
to administer SCCM so I can keep doing my job.  Powershell seems to be the one 
everyone likes so I’m trying to figure out how usable it is for full-time SCCM 
administration.

Ryan

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Ryan
Sent: Wednesday, July 9, 2014 12:53 PM
To: [email protected]
Subject: Re: [mssms] RE: Config Manager 2012R2 and Powershell


 


Is there a reason you don't want to use the console? I'm all for using 
Powershell as much as possible, but I generally use the console for day to day 
tasks. I only switch to Powershell when I have to automate setting multiple 
things or am searching for something specific (like all collections with 
incremental updates checked). 


 


Here is the Cmdlet reference for R2:  
http://technet.microsoft.com/en-us/library/jj821831(v=sc.20).aspx


Powershell changes in CU1: http://support.microsoft.com/kb/2932274


Powershell changes in CU2: http://support.microsoft.com/kb/2962855


 


 


 



On Wed, Jul 9, 2014 at 1:42 PM, Ryan Shugart <[email protected]> wrote:






Thanks everyone.  I thought 2012R2 was only at CU1 and not CU2?  We do have CU1 
installed.  I’ll look at the connect sites, but is there a good list comparing 
what you can do through the GUI and what you can do through the Powershell CLI? 
 Let’s look at basic tasks such as managing collections, managing software 
updates, managing applications that kind of thing.  Are those all covered 
through Powershell?

Thanks.

Ryan

 



From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Ratliff
Sent: Wednesday, July 9, 2014 12:10 PM



To: [email protected]
Subject: [mssms] RE: Config Manager 2012R2 and Powershell


 

Full time? No, there are some things you cannot do with PowerShell, such as 
edit task sequences. 

 

You can do a lot with WMI, but if you are going to use the native cmdlets make 
sure you are on 2012 R2 CU2. They have made a lot of updates to the cmdlets, 
and continue to. 

 

For an idea of any existing issues check out Connect. There are a lot of 
requests out there. 

 

https://connect.microsoft.com/ConfigurationManagervnext/Feedback 

 


Daniel Ratliff

 



From: [email protected] [mailto:[email protected]] On 
Behalf Of Ryan Shugart
Sent: Wednesday, July 09, 2014 1:59 PM
To: [email protected]
Subject: [mssms] Config Manager 2012R2 and Powershell

 


Hi all:




        Question.  I know that SCCM 2012R2 can be administered through 
Powershell.  Has anyone tried this fulltime, AKA used Powershell to admin SCCM 
completely in place of the SCCM console?  If so, any good guides on how to do 
this?  Any pitfalls, AKA areas Powershell just doesn’t cover?


Thanks.


Ryan


 


Ryan Shugart


LAN Administrator


MiTek USA, MiTek Denver


314-851-7414


 



MiTek Holdings, Inc., 2011-2014, All Rights Reserved 


  ________________________________  


This communication (including any attachments) contains information which is 
confidential and may also be privileged. It is for the exclusive use of the 
intended recipient(s). If you are not the intended recipient(s), please note 
that any distribution, copying, or use of this communication or the information 
in it is strictly prohibited. If you have received this communication in error, 
please notify the sender immediately and then destroy any copies of it. 

 

 


The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.

Reply via email to