-
- Service Provider
- Posts: 880
- Liked: 164 times
- Joined: Aug 26, 2013 7:46 am
- Full Name: Bastiaan van Haastrecht
- Location: The Netherlands
- Contact:
To v8 upgrade, alternative location
Hi,
We have a minor issue with the v8 installer (downloaded on the 24th of november).
v7 was installed on an alternative location. After the upgrade to v8, all existing components have upgraded in that location exept for the ActiveDirectoryExplorer. It's installed in the Windows default Program Files location.
I do not see a referending registry key to manualy correct this. We would like to move these components to our alternative location.
Known issue? Havent created support ticket yet.
Regards,
Bastiaan
We have a minor issue with the v8 installer (downloaded on the 24th of november).
v7 was installed on an alternative location. After the upgrade to v8, all existing components have upgraded in that location exept for the ActiveDirectoryExplorer. It's installed in the Windows default Program Files location.
I do not see a referending registry key to manualy correct this. We would like to move these components to our alternative location.
Known issue? Havent created support ticket yet.
Regards,
Bastiaan
======================================================
Veeam ProPartner, Service Provider and a proud Veeam Legend
Veeam ProPartner, Service Provider and a proud Veeam Legend
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: To v8 upgrade, alternative location
You might want to dig deep into installation .iso directly to \Explorers folder. Copy VeeamExplorerForActiveDirectory.msi and install it on whatever machine you want to; should do the trick. Thanks.
-
- Service Provider
- Posts: 880
- Liked: 164 times
- Joined: Aug 26, 2013 7:46 am
- Full Name: Bastiaan van Haastrecht
- Location: The Netherlands
- Contact:
Re: To v8 upgrade, alternative location
Hi Vladimir, yes that did it.
I run the VeeamExplorerForActiveDirectory.msi, this removed it from the default Program Files location. Ran it again, and installed to the alternative location, and it works. Thanks again!
I run the VeeamExplorerForActiveDirectory.msi, this removed it from the default Program Files location. Ran it again, and installed to the alternative location, and it works. Thanks again!
======================================================
Veeam ProPartner, Service Provider and a proud Veeam Legend
Veeam ProPartner, Service Provider and a proud Veeam Legend
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: To v8 upgrade, alternative location
You're welcome. Should other help be needed, feel free to ask. Thanks.
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: To v8 upgrade, alternative location
Active Directory Explorer was never a part of v7 to start with. It was a beta that we have released much later, and it used a separate installer.b.vanhaastrecht wrote:After the upgrade to v8, all existing components have upgraded in that location exept for the ActiveDirectoryExplorer.
-
- Service Provider
- Posts: 880
- Liked: 164 times
- Joined: Aug 26, 2013 7:46 am
- Full Name: Bastiaan van Haastrecht
- Location: The Netherlands
- Contact:
Re: To v8 upgrade, alternative location
True, perhaps I did not explain it well. I ment that the installer upgrades any existing component in its orogininal location. But the new ActiveDirectoryExplorer somehow ended up in the windows dedault Program Files location. As fas as i know, the beta version was never installed on this server.
======================================================
Veeam ProPartner, Service Provider and a proud Veeam Legend
Veeam ProPartner, Service Provider and a proud Veeam Legend
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: To v8 upgrade, alternative location
Bastiaan, if beta was never installed on the server, the behavior looks unexpected, so I've passed this thread to QC for further reproduction and addressing. Thanks for reporting.
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 60 guests