Tranquil IT Forum

Hello,

when machines are moved within Active Directory (a change of Organizational Unit), WAPT doesn't detect it and therefore doesn't apply the "unit" packages.

This is rather annoying when you expect a certain level of process automation.

Is it possible to force WAPT to detect that hosts have been moved?

Thanks in advance.
Tom

Hello t.heroult,

The OU that the WAPT agent reports is the one where the computer thinks it is located (not its actual location in Active Directory). If it's not updated, it means there hasn't been a gpupdate in the meantime. You can force it from the WAPT console by right-clicking on the computer and choosing: Then restart an inventory update.

Sincerely,

Denis Cardon

OK, thanks, it works.

Beyond that, there was another problem in Active Directory (I'm almost ashamed to admit it, but it predates my arrival): there are Organizational Units (OUs) with accented characters (like "Clients légers"), and unit assignment doesn't work on these OUs.

Great, that was the argument I needed to convince the IT department to restructure Active Directory a bit with more best practices.

I'm closing the topic.