I am trying to deploy Architecture 2012 (64 bit) on my network and have gone through the deployment, entering my network support folders, express tools options etc. Pretty easy, just like autocad 2008. the issue I am having is when I run the deployment installation on the workstations, I get only about half the TOOLs>OPTIONs support files settings when I start the program on the target workstations. And I don't get express tools. I have double and tripple checked my deployment and all the settings are correct.
I can change all the support file settings by hand and it works, but I can't get express tools.
I even installed a copy to another 64bit machine from the install cd and changed all the settings by hand just to be sure all the paths are correct and that machine works great. I would rather use the deploy since I have 15 machines to install.
All are 64 bit Win 7 machines. Any ideas?
Are you deploying from a UNC path or a mapped drive? Full write access to the share? If you type EXPRESS in the command line, do you get the express tools?
For the 64 bit deploys I have used UNC because when I use a mapped drive in the file locations, the install fails immediatly, even if the local machine has the mapped drive in use.
I have done the deployment install on each ws with the user logged on. Each user is an administrator on the ws they are using.
I also set the deploy to "non silent" mode so I can be sure of the setting as the install progresses.
For the admin image location, and the shared file location, I am using the same drive that we used for ACAD2008. XP 32 bit 2008 worked like a champ. Now with Win7 and 64 bit it has issues. Confusing.
Even 64bit Win7 with ACAD2008 deployed properly, but had some weird issue during use, hence the upgrade.
One other thing, if I type ExpressTools at the command prompt, it says invalid command.
The machine that I installed from disk, loaded the express tools menu when I ran the expresstools command.
Interesting indeed. It sounds like you did everything correctly. You are running the shortcut in the root of the share, correct? The share has full write access as well, correct? Very odd behavior.
Travis, thanks for the info and attention. I have been making the depoys on my 64 bit laptop connected to the network via cable. A think I will try to refresh the deploy from a permanent workstation and see if that changes it. I have had issues with laptops accessing shares on our network in the past.
It's certainly worth a try. I typically try to make the deployment from the server that will host the deployment. As long as the share is set and the workstation can access the UNC path, you should be fine. Update this post if you have further information. Good luck!