ravaged1 Posted July 16, 2015 Posted July 16, 2015 timmy2, you should be able to get the info you need, either by accessing the registries remotely or via power shell command-let.
spudw2k Posted July 16, 2015 Posted July 16, 2015 Considering the OP's Access Denied error, that tells me that the WMI is running but authentication failed, which is bizarre since you can browse to C$ and ADMIN$. Spoiler Things I've Made: Always On Top Tool ◊ AU History ◊ Deck of Cards ◊ HideIt ◊ ICU ◊ Icon Freezer ◊ Ipod Ejector ◊ Junos Configuration Explorer ◊ Link Downloader ◊ MD5 Folder Enumerator ◊ PassGen ◊ Ping Tool ◊ Quick NIC ◊ Read OCR ◊ RemoteIT ◊ SchTasksGui ◊ SpyCam ◊ System Scan Report Tool ◊ System UpTime ◊ Transparency Machine ◊ VMWare ESX Builder Misc Code Snippets: ADODB Example ◊ CheckHover ◊ Detect SafeMode ◊ DynEnumArray ◊ GetNetStatData ◊ HashArray ◊ IsBetweenDates ◊ Local Admins ◊ Make Choice ◊ Recursive File List ◊ Remove Sizebox Style ◊ Retrieve PNPDeviceID ◊ Retrieve SysListView32 Contents ◊ Set IE Homepage ◊ Tickle Expired Password ◊ Transpose Array Projects: Drive Space Usage GUI ◊ LEDkIT ◊ Plasma_kIt ◊ Scan Engine Builder ◊ SpeeDBurner ◊ SubnetCalc Cool Stuff: AutoItObject UDF ◊ Extract Icon From Proc ◊ GuiCtrlFontRotate ◊ Hex Edit Funcs ◊ Run binary ◊ Service_UDF
timmy2 Posted July 17, 2015 Author Posted July 17, 2015 Did you enable remote management on the other computers? I opened an elevated command prompt and ran the following command on the target PC:winrm quickconfig Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>winrm quickconfig WinRM is not set up to receive requests on this machine. The following changes must be made: Set the WinRM service type to delayed auto start. Start the WinRM service. Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users. Make these changes [y/n]? y WinRM has been updated to receive requests. WinRM service type changed successfully. WinRM service started. Configured LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users. WinRM is not set up to allow remote access to this machine for management. The following changes must be made: Create a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine. Enable the WinRM firewall exception. Make these changes [y/n]? y WinRM has been updated for remote management. Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine. WinRM firewall exception enabled. C:\Windows\system32> I thought it was interesting that the program's output recommended adding the LocalAccountTokenFilterPolicy key, which I had already done. Made me think I was on the right track.I rebooted the target PC and then tried the OP code, but the above changes still did not prevent the Access Denied errors.Stymied.
timmy2 Posted July 17, 2015 Author Posted July 17, 2015 timmy2, you should be able to get the info you need, either by accessing the registries remotely or via power shell command-let.Hey, I'll take any method I can get -- given instructions.
ravaged1 Posted July 17, 2015 Posted July 17, 2015 (edited) Well I need to ask if you tried disabling the fire wall on a target computer, even though you probably have.This is the remote admin command I was referring to. https://technet.microsoft.com/en-us/library/Cc738900(v=WS.10).aspx As far as the other methods, Google is your friend.I believe you can use the reg command and specify a remote computer not sure the syntax. and powershell can do all kinds of wonderful things.(may need a command-let)In truth though sometimes simple is the best way, and having a startup script on the computers that dumps that info some place for you to retrieve might be the easiest. Edited July 17, 2015 by ravaged1 spelling
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now