Hmmm... where is the Problem...?
1st is to set Create object... check Ignore... uncheck Create...
I have no new devices in my LDMS... :-)
you Need the LDAP Property userAccountControl This represent the disabled or enabled state
4096 is enabled and 4098 ist disabled... (for Workstations)
Please have a look at this page:
I have this setup in my environment, if that device exists in LANDesk and the name matches a device in AD then no matter if its enable or disabled it will update the fields you have assigned, that check to ignore disabled devices is only for creating an entry in LANDesk for devices that dont exist, this is script i have for importing whether enabled or disabled. I am mapping to a field I created called AD Status. Hope this helps!
OK... so I do that check/uncheck sequence and have both of the boxes unchecked when I hit the finish button. That all makes sense to me, but when I go back into the rule to confirm the settings, it shows the "ignore disabled objects" checked, not as I had left it. Could this be an issue with the DA install on my core server? It does the same thing on a remote console as well as directly on the core.
no, that check is ONLY if you have the box to create objects created, if you are looking to just update your existing LANDesk records then those boxes don't apply to what you're doing and you can ignore them. Just setup the rule to map the "useraccountcontrol" field in AD to a field in your inventory like my screenshot, it will work whether disabled or not.
Yup, I guess I was getting confused about the greying out aspect of the check boxes. I did run a test rule one time on my test core and it populated a whole bunch of computer accounts that weren't in inventory, which is what I was trying to avoid. I must have set the rules on that test wrong.
I created a rule as you stated and it is working as I wanted it to. I am new to DA, so I am just starting to learn the subtle nuances of this product. The help doc on this feature was rather thin on this. Thanks for your help.