I've never done this - usually I backup my publisher configs/tasks and I reinstall QlikView. It should not take more than an hour to do that. If your publisher config isnt that complex, you can also just rebuild the jobs.
Moving machines from one domain to another can sometimes cause weird issues. Issues that take hours to figure out, troubleshoot and fix.
Thanks for the point.
In fact, i'm more worried about the users access.
I have 700 to 800 users, the big-bang method could kill the administrator if the publisher can't distribute to the right users.
I'm making an assumption, IF the QWS works like the IIS, thereotically there's nothing to be done, besides the new LDAP to be configured in the Directory service connector.
But i still need to test this ....
Currently is on old domain, it will be joined to the new domain with the new AD.
I am still thinking it will work.
Because, we are duplicating the old AD to became the new one.
and to QV, only the cn * SAMAccount object matters.
cn is for direct distribution by publisher and SAM is for section access.