Attempting to perform the above on a non-imaged / pre installed version of Landesk Agent.
Maybe its our LANDesk Agent installed with our deployed windows image...
Installing using a recovery Windows XP Sp2 cd...
Will keep you all posted
1 of 1 people found this helpful
Mangement Gateway will reject machines that hae matching GUID's. Make sure you delete the GUID if you are going to create an image with the agent installed.
Good one! Will do. So far the imaging process we use will create a unique GUID. But the method I was using for testing was not. I'll keep that in mind for future tests Thanks!
Update - Looks like it is our security settings on our standard XP image. The bare bones XP Sp2 install worked like a champ.
We have another test to try evolving WMI security settings. I'll keep you all posted on that process. I have not heard anyone else having this issue, but if we solve it, I'll be sure to post our solution.
Update - No good. WMI settings were not our issue.
Looks like something to do with a security setting 'somewhere' amongst our image. Up hill battle from here. Thanks for everyones help!
I'm pretty sure I've seen a "new SID generator" a few years ago somewhere - I can't find it at the moment, but that may help you.
What kind of image are you using - not sysprep (I imagine) - since sysprep should (I say "should" but I've seen otherwise) generate new SID's for clients ... but if you can find the generator, that may save you a fair bit of work in terms of fixing this :).
LANDesk EMEA Technical Lead.