I can remember an incident, whenever i did try to open the script editor, it showed an error related registry. I deleted my windows profile from AW being local admin, and logged in again with my domain user and found the issue resolved.

As you should. Your original scenario was wrong.

A client Admin Workstation has to join the ICM domain. It makes perfect sense that you should log in on the domain. In ICM, you can create users which are pushed up to the DC (have to obey password rules) and are created therein. Now they are domain logins. Why not use them?

Back to the original problem. The script editor can do this whether it's on a Client AW or even a Distributor AW. There is no rhyme or reason - it just happens. When it does, do as Chad suggested - find scripted.exe in the task manager and bump it off.

Regards,

Geoff

Works fine now, many thanks Chad (and Geoff)