Databases
StackOverflow2013
Postsdbo
POGet-WmiObject credentials not working when scheduled
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGet-WmiObject credentials not working when scheduled
    primarykey
    data
    text
    <p>I have a Powershell script to detect disk space on a network server that requires a user/password to access it.</p> <p>I followed this: <a href="http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/440ab7ed-7727-4ff7-a34a-6e69e2dff251/" rel="nofollow">http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/440ab7ed-7727-4ff7-a34a-6e69e2dff251/</a></p> <p>To get this code:</p> <pre><code>$password = get-content C:\creds.txt | convertto-securestring $cred = new-object -typename System.Management.Automation.PSCredential -argumentlist "username",$password Get-WmiObject -ErrorAction Stop Win32_LogicalDisk -ComputerName $deviceName -credential $cred -Filter "DeviceID='$darg'" </code></pre> <p><code>$deviceName</code> and <code>$darg</code> are already correctly defined.</p> <p>This works just fine when running the Powershell script manually. But when I set it up as a Windows schedule task, it fails thinking the user/pass is incorrect:</p> <blockquote> <p>Get-WmiObject : Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESS DENIED))</p> <p>$disks = Get-WmiObject &lt;&lt;&lt;&lt; -ErrorAction Stop Win32_LogicalDisk -ComputerName $deviceName -credential $cred -Filter "DeviceID='$darg'" + CategoryInfo : NotSpecified: (:) [Get-WmiObject], Unauthorized AccessException + FullyQualifiedErrorId : System.UnauthorizedAccessException,Microsoft.PowerShell.Commands.GetWmiObjectCommand</p> </blockquote> <p>Why is this? (The account is a local user on the remote server. I've tried entering the credentials on the Schedule interface but it doesn't let me save it, saying invalid login; maybe due to being a local account) <code>ServerName\LocalUser</code> does not work in the Windows Schedule UI, still gives the incorrect login error.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJBurace
    1. USJBurace
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COTry using ServerName\LocalUser as the username. Consider that the specified account must be a user of the local administrators group on the target server.
      singulars
      1. POGet-WmiObject credentials not working when scheduled
      1. USRex Hardin
    2. COI am under the impression that convertto/from-securestring works on a per-user basis if you don't provide a specific key value. IOW, one user can't read another user's data. This pre-existing SO question seems relevant: http://stackoverflow.com/questions/7109958/saving-credentials-for-reuse-by-powershell-and-error-convertto-securestring-ke. There is also relevant information discussion at Powershellcommunity.org: http://powershellcommunity.org/Forums/tabid/54/aft/8122/Default.aspx
      singulars
      1. POGet-WmiObject credentials not working when scheduled
      1. USdarin strait
    3. CO@darinstrait That was it, thanks. Feel free to drop that as an answer and I'll accept.
      singulars
      1. POGet-WmiObject credentials not working when scheduled
      1. USJBurace
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload