Switch to the Bing Ads Community
Switch to the Microsoft Advertising Community
Grow your business by advertising on Bing, Yahoo! Search and our syndicated search partners!
Trouble logging in? Need help with managing your account?
Contact Bing Ads Support now.
I'm managing this tool for really long time and I had a lot of bugs and sometimes I feel it is going to be better.. No it isn't.. MSI deployment is done absoultelly without thinking for business users with requirement to group deploy and it is still like going in a circle. After months of communicating the MSI package was available for methen it is fine for some time, then the URL change and you need to find the right one (that happened to me twice). Now the MSI package URL is public but it is not working like it was working before.. The installed tool MSI package is deployed to deployment acocunt profile and to get it work under all other profiles I'm just in process of investigating and doing MYSELF. Also some distributions when you are uninstalling them via MSI are also removing SQL server some of them no - there is no rule about that but simply if the software didn't install it why it is uninstalling it??? Also it is great that the requirements for SQL server changed without any bigger note from SQL Server Express 2008 to SQL Server Express 2008R2.
The tool is on the market for more then 1 year and it is going huge steps back with MSI deployment.
Workaround how to get it work:
I have an update..
I played a bit with the package and found following:
* Repacking and changing MSI file values through ORCA is not good idea and it is not working..
* parametres for MSI are partially working -> this can solve the issue with deployment for all users
- 32bit deployment parametres - TARGETDIR="C:\Program Files" INSTALLDIR="C:\Program Files"
- 64bit deployment parametres - TARGETDIR="C:\Program Files (x86)" INSTALLDIR="C:\Program Files (x86)"
Hope it helps..
Note for developers:
I've never seen another product saying in a version 7.9 (!!!) and many years of development it is a BETA version.. Maybe it means - Here is a product which may works but help yourself..
I'm fine with that when developers are listening the needs and the product is doing better and better but fairly I don't see it this way right now..
I'm installing it with following:
msiexec /i adcenter.msi /q /norestart TARGETDIR="C:\Program Files (x86)\Microsoft AdCenter Desktop" INSTALLDIR="C:\Program Files (x86)\Microsoft AdCenter"
This way you are able to deploy into location you would like to but the shortcuts you need to do manually.. Uninstallation this way works as well.
I also tried to edit MSI with ORCA to correct the settings from developers but it was corrupting whole package and mentioned solution above was faster to test and implement then debug what is wrong with repacking..
Sorry previous uncomplete post..
msiexec /i adcenter.msi /q /norestart TARGETDIR="C:\Program Files
(x86)\Microsoft AdCenter Desktop" INSTALLDIR="C:\Program Files
(x86)\Microsoft AdCenter Desktop"
msiexec /i adcenter.msi /q /norestart TARGETDIR="C:\Program Files\Microsoft AdCenter Desktop" INSTALLDIR="C:\Program Files\Microsoft AdCenter Desktop"
The Desktop MSI was changed to allow for limited-users to install/upgrade the tool themselves. IT Admins in managed environments need only distribute the pre-requisites: Windows Installer 4.5, .NET 4.0, and SQLExpress 2008 RS as described in the Remote Installation Guide. Once these pre-requisites are installed the local user can run the Desktop MSI from the download site and install / update it themselves.