Cached Credential utility, not starting

If you are testing, set a date to the past. 

When that date is past, and the UNC Path exists, the ini files is checked for the logged on user. If the user exist in he map, the utility runs and prompts the user for their target password. At that point is process, backs up the cached cred and moves the workstation. 

If you are testing, set a date to the past. 

When that date is past, and the UNC Path exists, the ini files is checked for the logged on user. If the user exist in he map, the utility runs and prompts the user for their target password. At that point is process, backs up the cached cred and moves the workstation. 

thanks Jeff. 

 I tried that also with a date in the past but it still didnt invoke.
Do the server locations for the vmove and other bits actually have to be remote shares? I just copied these items locally and configured all the scripts to refer to local path.  the VPN clients dont have access to any shares like this

Yes, they have to be on a remote share. Also a target domain controller has to be available too.  The tool is designed to see that changes to the network and the share existing as a sign it can do everything it needs to. 

ok, I've reconfigured this for a network share that the client can access, but still nothings happening. Are there any logs or any way to manually invoke it?

The simplest way is to start and stop the service. Also is everything is in place, just installing the service will launch it as soon as the service starts. 

but when it's not starting.. is there any way to troubleshoot it?

Your best bet is to all support. I don’t remember off the top of my head and I would have lab it to remember. The utility runs as a service. It runs as local system. So assuming it is installed and configure properly it should create a log.  If you don’t see logs, the service is not running. 

I got it going, there was a syntax error in the config file. The Quest online docco says to use target domain controller for DNS but the app requires the domain name, not the DC. 
However, I then got stuck with that old chestnut the duplicate SPN when joinging the target domain ( I am doing child to parent domain migrations) I have been avoiding having to hack AD to disable this check, but I may be forced to now