/build/static/layout/Breadcrumb_cap_w.png

Bartender 2019 R5

Hi,

Anyone here who has succeded in deploying Bartender 2019 R5 (x64) to Windows 10 using SCCM? It works great if I put the install information in an .cmd-file and run this with my AD admin account but with SCCM the SYSTEM account is used and somehow this isn't working out so great. It will only install about 50-60% of the installation but then fails.

Whitepapers can be found here.. https://www.seagullscientific.com/media/1677/bartender-silent-install-201908.pdf

We use this command


setup.exe FEATURE=BarTender INSTALLSQL=true BLS=MyBLSServer:5160 PKC=xxxx-xxxxxxxx-xxxx


The first answer from seagull support is that they recommend us to install with a local admin account but that can't be done due to security restrictions.


0 Comments   [ + ] Show comments

Answers (2)

Posted by: jonniipalos 4 years ago
Red Belt
0

I know you said you can't use local admin but what about an AD service account? that's what we ended up having to do at my last job. We set up the service account with admin access but limited it's login ability and even it's login times just to be safe and that allowed the software to go through without making our CSO mad.


I doubt it would do anything but its a worth a shot as well: can you try using the FQDN for the BLS? May be a faster test than the first recommendation.

Posted by: rileyz 4 years ago
Red Belt
0

We use ConfigMgr 1906 at our site, and we have found quite a few issues with installers running in 64-bit mode. Even though the software is 64-bit, it has issues using a 64-bit process during the install, I think it has something to do with memory. The symptoms are like yours, it works 50% of the time.


Anyway, the crux is - tick the box to run the installer in a 32-bit process. Give that a go and see what happens.

Remember to use the Control Panel applet, or from the ConfigMgr console if you want to force the install - if you use "Software Center" to force the install, its not the same as from the the control panel or console.

*ignore uninstall, i just pinched this from the internet.

Programs-Tab-in-Deployment-Type-for-32-bit-application-installer.png?w=666&ssl=1


Comments:
  • The "run installation and uninstall program as 32-bit.." is used by default. Sorry too say that this doesn't work either. - Barahir 4 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ