Thanks Chris.

I don't need any interaction change the resolution. The nircmd runs 
successfully either manually or remotely with psexec without any interaction 
required.

Not sure why task sequence is failing but psexec succeeds when both are using 
system account.



From: [email protected] [mailto:[email protected]] On 
Behalf Of Brucker, Chris
Sent: Monday, October 27, 2014 12:32 PM
To: [email protected]
Subject: [mssms] RE: mass change resolution

You may have to use ServiceUI before nircmd to interactively change the 
resolution. It requires that you install the Microsoft Deployment Toolkit. Once 
it is installed, navigate to the Tools folder on the deployment share.

Johan Arwidmark has a great blog post about how to use it:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/65/Troubleshooting-CM2012-Task-Sequence-Actions-Using-ServiceUI.aspx

Let me know if you have any questions, I would be happy to help.

Thanks,
Chris Brucker
First Financial Bank | IT - Desktop Engineer
Suite 800 | 225 Pictoria Dr. | Cincinnati, OH 45246
513-551-1673

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Timothy Ransom
Sent: Monday, October 27, 2014 12:28 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: mass change resolution


I still get same results with or without run as accounts - executable starts 
but does not change resolution.

But the same command line succeeds using psexec from remote computer.

psexec \\computername<file:///\\computername> -s -i  \\share\nircmd.exe 
setdisplay 1152 964 
32<file:///\\share\nircmd.exe%20setdisplay%201152%20964%2032>

I read recently that should not have to use psexec with sccm.

Anyone else experience this type of issue before?

I am open to using psexec, have used it many times but would like the 
convenience and reporting of SCCM  due to 100+ remote sites.



From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of John Aubrey
Sent: Friday, October 17, 2014 12:17 PM
To: '[email protected]'
Subject: [mssms] RE: Multires to mass change resolution

This is what I use in my task sequence for our clock in and out stations.  I 
don't have anything under the run as account in the TS, works flawlessly.

http://12noon.com/?page_id=80<https://urldefense.proofpoint.com/v2/url?u=http-3A__12noon.com_-3Fpage-5Fid-3D80&d=AAMFAg&c=WE0At5E24laHU5j4-pDiGCY8tBHoG528XbY2mQA7QzI&r=1PQtgD4rMoHBI9wGXS5RjtJCnC_HUSxR5kLNDPYWBYc&m=2-xw8e0sCttY7Cc51HC-LF0i3pwYnVR6ZaR_O-fHQP8&s=lHCiSr_yIJ6ZTMw0MVAGIyKyhYdDywmoEKk784pnPdY&e=>


dc64.exe -width=800 -height=600 -depth=32 -refresh=60 -force -quiet

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Timothy Ransom
Sent: Friday, October 17, 2014 12:07 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Multires to mass change resolution

Hi,

I need to change resolution on about 1800 PCs and Group Policy is not an option 
in this case.
Multires works perfectly when run locally but just hangs when run from SCCM 
package or ts.

Has anyone used Multires in batch or script before and resolved this issue?

Thanks,
Tim

**********************************************************************************************
GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential 
information protected by state or federal law. The information is intended only 
for use consistent with the state business discussed in this transmission. If 
you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or the taking of any action based on the 
contents is strictly prohibited. If you have received this transmission in 
error, please delete this email and notify the sender immediately. Your 
cooperation is appreciated.
**********************************************************************************************




**********************************************************************************************
GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential 
information protected by state or federal law. The information is intended only 
for use consistent with the state business discussed in this transmission. If 
you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or the taking of any action based on the 
contents is strictly prohibited. If you have received this transmission in 
error, please delete this email and notify the sender immediately. Your 
cooperation is appreciated.
**********************************************************************************************


________________________________
The information contained in this message from First Financial Bancorp or its 
affiliates and any attachments are confidential. It is not intended for 
transmission to, or receipt by, anyone other than the addressee(s), or a person 
authorized to deliver it to the named addressee(s). If you have received this 
message in error, you are prohibited from copying, distributing or using the 
information. Please contact the sender immediately by return email and delete 
the original message.

**********************************************************************************************
GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential 
information protected by state or federal law.  The information is intended 
only for use consistent with the state business discussed in this transmission. 
 If you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or the taking of any action based on the 
contents is strictly prohibited.  If you have received this transmission in 
error, please delete this email and notify the sender immediately.  Your 
cooperation is appreciated.
**********************************************************************************************



Reply via email to