/build/static/layout/Breadcrumb_cap_w.png

Windows XP machines - OS unknown - can't do distributions

I have a location where the tech has a different image than the rest of us. I went to deploy IE8 this weekend to upgrade from IE7, but noticed that most machines weren't showing up in the list of distributions. After some research, it seems as if the hardware details/summary and OS is unknown and glitchy - so it won't distribute. However, if I do a RUN NOW script with no OS restrictions, it works. But I need to use the distribution method.

 

Any ideas? They should all be XP SP3 and have the latest client on them.


0 Comments   [ + ] Show comments

Answers (4)

Answer Summary:
The permissions on “My Computer†in “component services†for “Access Permissions and Launch and Activation Permissions†are not set correctly Open “Component Services†from “Administrative Tools†or with command “C:\WINDOWS\system32\Com\comexp.mscâ€. Expand “Computer†section. Select “My Computer†object and open “Properties†dialog box. Go to “COM Security†tab. Set theses permissions for “Edit Limits†and “Edit Default†in section “Access Permissions†Edit Limits Anonymous Logon => Local Access + Remote Access Distributed COM Users => Local Access + Remote Access Everyone => Local Access + Remote Access Edit Default SELF => Local Access + Remote Access SYSTEM => Remote Access Set theses permissions for “Edit Limits†and “Edit Default†in section “Launch and Activation Permissions†Edit Limits Administrators => Local/Remote Launch + Local/Remote Activation Distributed COM Users => Local/Remote Launch + Local/Remote Activation Everyone=> Local Launch + Local Activation Offer Remote Assistance Helpers => Local/Remote Launch + Local/Remote Activation Edit Default Administrators => Local/Remote Launch + Local/Remote Activation INTERACTIVE => Local/Remote Launch + Local/Remote Activation SYSTEM => Local/Remote Launch + Local/Remote Activation !!! MANDATORY !!! REBOOT COMPUTER Test if connectivity is working with “Windows M;anagement Instrumentation Testerâ€, to do this see the last section of this document
Posted by: sfigg 11 years ago
Red Belt
3

ok I found the solution - it was WMI permissions. I followed these steps to fix it. There is also a script that can do this for you, but I can't attach it here.

 

he permissions on “My Computer” in “component services” for “Access Permissions and Launch and Activation Permissions” are not set correctly
  1. Open “Component Services” from “Administrative Tools” or with command “C:\WINDOWS\system32\Com\comexp.msc”.
  2. Expand “Computer” section.
  3. Select “My Computer” object and open “Properties” dialog box.
  4. Go to “COM Security” tab.
 http://www.simple-tech.info - You receive an Access is denied error when you want to connect a remote computer / server with WMI and use the user credentials
 
  1. Set theses permissions for “Edit Limits” and “Edit Default” in section “Access Permissions”
Edit Limits
Anonymous Logon => Local Access + Remote Access
Distributed COM Users => Local Access + Remote Access
Everyone => Local Access + Remote Access
 
Edit Default
SELF => Local Access + Remote Access
SYSTEM => Remote Access
  1. Set theses permissions for “Edit Limits” and “Edit Default” in section “Launch and Activation Permissions”
Edit Limits
Administrators => Local/Remote Launch + Local/Remote Activation
Distributed COM Users => Local/Remote Launch + Local/Remote Activation
Everyone=> Local Launch + Local Activation
Offer Remote Assistance Helpers => Local/Remote Launch + Local/Remote Activation
 
Edit Default
Administrators => Local/Remote Launch + Local/Remote Activation
INTERACTIVE => Local/Remote Launch + Local/Remote Activation
SYSTEM => Local/Remote Launch + Local/Remote Activation
  1. !!! MANDATORY !!! REBOOT COMPUTER
  2. Test if connectivity is working with “Windows M;anagement Instrumentation Tester”, to do this see the last section of this document

 

 


Comments:
  • Awesome, glad you figured it out. - jknox 11 years ago
  • Nice job and thanks for sharing the fix!!! I ran into this with one of my XP machines as well but didn't get as deep since it was replaced not long after I discovered the problem.

    John - jverbosk 11 years ago
Posted by: jknox 11 years ago
Red Belt
2

Offhand, I'd say WMI is corrupted on that machine. You can test this by running this in a command prompt: wmic os get name

If WMI is working, it will return Windows XP.  If not, try repairing it: http://www.microsoft.com/en-us/download/details.aspx?id=7684


Comments:
  • Thanks - I stayed up late last night working on this. I did a WMI integrity check, and WMI was fine - but there were a bunch of "access denied" errors. Turns out the service "RPC" was being run as NT AUTHORITY\Network Service....not sure why....but when I changed it to local system, rebooted, updated inventory - and now it shows everything! - sfigg 11 years ago
  • Ugh - actually - i just ran a batch file on 400 machines to change RPC to local system, restarted, and forced update. It doesn't update now.

    I did the OS WMIC command above, and I get access denied. - sfigg 11 years ago
Posted by: sfigg 11 years ago
Red Belt
1

Gets even weirder - so I force a RUN NOW, and IE8 installs fine. However, it doesn't show up under the installed programs list after the inventory updates. It has for other locations. I removed the PC from KACE inventory - then it checked back in....and now there are NO programs listed under the installed programs list.

 

there are close to 300 machines that I can tell are messed up (at least need IE8 so those are the ones I'm aware of).


Comments:
  • I just did a reinstall of the client, and it stays the same.

    Here is a screenshot of what I'm seeing after a reinstall of the agent:
    https://dl.dropbox.com/u/119117/kace2.PNG - sfigg 11 years ago
Posted by: sfigg 11 years ago
Red Belt
1

Here is the page where I got the 2 scripts from:

 

http://community.spiceworks.com/topic/7994-here-is-a-script-to-enable-configure-dcom

 

I pushed those out via RUN NOW, rebooted the machines, then forced an inventory update, and 791 out of 800 machines were fixed.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ