Network Drives and printers
New tool shows the NW drives and NW printers where as the current agent is inconsistent at best.
Hopefully the new tool funtionality will be incorporated into the next agent release.
Hopefully the new tool funtionality will be incorporated into the next agent release.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
mikergray
14 years ago
Glad to hear you like the new tool. We are definitely planning to use the functionality of the new tool in a future revision of the K1000.
I do not know for sure, but I would guess the inconsistency around discovering network drives and printers in the current version is related to running the K1000 agent service as LocalSystem whereas you are likely running the System Inventory Tool as a logged-in user. The network access restrictions of the LocalSystem account are Microsoft policies, so it is not clear to me that the new tool will fix the behavior you are seeing once it is used in the K1000.
You might try running the System Inventory Tool as Local System to see what information is collected or not collected. To do this testing, I recommend using psexec, from Windows Sysinternals team, as described here:
http://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
Would be great to hear your results if you get around to trying it!
I do not know for sure, but I would guess the inconsistency around discovering network drives and printers in the current version is related to running the K1000 agent service as LocalSystem whereas you are likely running the System Inventory Tool as a logged-in user. The network access restrictions of the LocalSystem account are Microsoft policies, so it is not clear to me that the new tool will fix the behavior you are seeing once it is used in the K1000.
You might try running the System Inventory Tool as Local System to see what information is collected or not collected. To do this testing, I recommend using psexec, from Windows Sysinternals team, as described here:
http://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
Would be great to hear your results if you get around to trying it!
Posted by:
Spyder2114
14 years ago
This used to work back in the 1.5-2.0 days but stopped somewhere between 2.0 and 4.0. We have tested all scenarios of user login and credentials to no avail. I'll try what you suggested and post the results here.
Thanks
Thanks
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.