Thanks for the suggestion to contact Sectigo -- they responded immediately with exactly what I needed. It turns out there's a setting for this!
You can "Enable Single Logon" which will not prompt you to enter the password every time but it is only valid until screen locks. You can Enable this by ...
Suggested Articles
Search found 63 matches
- Fri Dec 08, 2023 2:07 pm
- Forum: Building Installers
- Topic: avoid entering code signing password multiple times
- Replies: 5
- Views: 30912
- Jump to post
- Wed Dec 06, 2023 2:43 pm
- Forum: Building Installers
- Topic: avoid entering code signing password multiple times
- Replies: 5
- Views: 30912
- Jump to post
Re: avoid entering code signing password multiple times
Thanks, Catalin. My token is from Sectigo in case you have better luck contacting them for some reason.
- Tue Dec 05, 2023 9:55 pm
- Forum: Building Installers
- Topic: avoid entering code signing password multiple times
- Replies: 5
- Views: 30912
- Jump to post
avoid entering code signing password multiple times
I renewed our code signing certificate this month and it was delivered as a physical token rather than a .cer or .pfx file. I activated the token so it's now in the local certificate store and it works fine. The only issue is that I'm required to enter the token password half a dozen times when ...
- Tue Sep 07, 2021 5:18 pm
- Forum: Building Installers
- Topic: stop install if app bitness is wrong
- Replies: 3
- Views: 11523
- Jump to post
Re: stop install if app bitness is wrong
@Catalin: I would have liked to use custom Launch Conditions but, unless I'm mistaken, I can't control the sequence of execution, which means I can't guarantee that the bitness check will be first. If that's not correct, please let me know.
Regardless, I tried your suggestion and it works fine. The ...
Regardless, I tried your suggestion and it works fine. The ...
- Tue Aug 31, 2021 4:59 pm
- Forum: Building Installers
- Topic: stop install if app bitness is wrong
- Replies: 3
- Views: 11523
- Jump to post
stop install if app bitness is wrong
Thanks to several helpful threads here I know how to determine the bitness of an Office app, which I need to do prior to installing my add-in.
However, unlike @Catalin's excellent tutorial and sample installer, I don't have a mixed bitness install. Instead, if the bitness is wrong I want to halt ...
However, unlike @Catalin's excellent tutorial and sample installer, I don't have a mixed bitness install. Instead, if the bitness is wrong I want to halt ...
- Mon Feb 10, 2020 3:01 pm
- Forum: Building Installers
- Topic: Reg value not being included in all builds
- Replies: 9
- Views: 7302
- Jump to post
Re: Reg value not being included in all builds
Unfortunately, I don't have a specific suggestion. Making the selectors larger and more prominent would probably help a bit. It would be great if they were located in the main working area of the app rather than on the ribbon, but I don't think that's practical. So I guess we're back to leaving them ...
- Thu Feb 06, 2020 3:05 pm
- Forum: Building Installers
- Topic: Reg value not being included in all builds
- Replies: 9
- Views: 7302
- Jump to post
Re: Reg value not being included in all builds
Thank you -- you found the problem! I was certain that I was overlooking a setting somewhere in the installer that was causing the problem but couldn't find it.
Thanks also for explaining more about registry redirection; it's a subject I don't know enough about and have been confused by in the past ...
Thanks also for explaining more about registry redirection; it's a subject I don't know enough about and have been confused by in the past ...
- Wed Feb 05, 2020 4:39 pm
- Forum: Building Installers
- Topic: Reg value not being included in all builds
- Replies: 9
- Views: 7302
- Jump to post
Re: Reg value not being included in all builds
Catalin,
Thanks for your suggestion but I'm not certain that's the source of the problem. The "StencilPath_2016" and "TemplatePath_2016" entries are not under the PRO_only feature, they are part of a long list of components that are included in every build -- note the level of indentation under the ...
Thanks for your suggestion but I'm not certain that's the source of the problem. The "StencilPath_2016" and "TemplatePath_2016" entries are not under the PRO_only feature, they are part of a long list of components that are included in every build -- note the level of indentation under the ...
- Fri Jan 31, 2020 3:18 pm
- Forum: Building Installers
- Topic: Reg value not being included in all builds
- Replies: 9
- Views: 7302
- Jump to post
Re: Reg value not being included in all builds
Thanks, Catalin. I wasn't expecting you to know precisely what was wrong! But I hoped there might be an obvious place or two for me to look for something I had missed.
I'll send the requested files to you shortly.
I'll send the requested files to you shortly.
- Thu Jan 23, 2020 10:25 pm
- Forum: Building Installers
- Topic: Reg value not being included in all builds
- Replies: 9
- Views: 7302
- Jump to post
Reg value not being included in all builds
This is driving me crazy! I'm sure I'm missing a setting somewhere but can't find it.
My installer has two builds, one for Standard and one for Professional.
It also includes one main feature and two sub-features:
The main feature is included in all builds and contains several dozen components ...
My installer has two builds, one for Standard and one for Professional.
It also includes one main feature and two sub-features:
The main feature is included in all builds and contains several dozen components ...
- Thu Jun 20, 2019 1:59 pm
- Forum: Building Installers
- Topic: change current per-user install so IT admins can run it
- Replies: 2
- Views: 3097
- Jump to post
Re: change current per-user install so IT admins can run it
A further thought on my question above -- my real objective is to create an installer that can be used in either of two ways:
1) a user logs in with their own account, runs the installer, preferably without requiring admin rights, and ends up with a per-user install
2) an IT admin logs in to the ...
1) a user logs in with their own account, runs the installer, preferably without requiring admin rights, and ends up with a per-user install
2) an IT admin logs in to the ...
- Wed Jun 19, 2019 5:56 pm
- Forum: Building Installers
- Topic: change current per-user install so IT admins can run it
- Replies: 2
- Views: 3097
- Jump to post
change current per-user install so IT admins can run it
Our current installer is set to install per user, which we've done for reasons related to the licensing of our app. However, an increasing number of our customers want to install while logged into an IT admin account on the user's machine. Naturally, a per-user install doesn't do any good because ...
- Thu Feb 04, 2016 7:52 pm
- Forum: Building Installers
- Topic: per user install run by admin
- Replies: 1
- Views: 2740
- Jump to post
per user install run by admin
I've failed to find the correct combination of settings to achieve this result: I want a per-user install, but the installer needs to be run by either 1) an end user with admin rights, or 2) an admin on behalf of a standard user.
#1 is easy. For #2, on a system where the standard user name is Scott ...
#1 is easy. For #2, on a system where the standard user name is Scott ...
- Fri Apr 10, 2015 2:32 pm
- Forum: Building Installers
- Topic: prepending value to registry entry
- Replies: 4
- Views: 4720
- Jump to post
Re: prepending value to registry entry
Thanks, Dan. That does explain what's happening. I'll continue with my original approach of using a custom search.
For the second part of my question: is there any way other than using a custom action to remove the string I've added during uninstall (I'm currently using VB script). For example, if ...
For the second part of my question: is there any way other than using a custom action to remove the string I've added during uninstall (I'm currently using VB script). For example, if ...
- Wed Apr 08, 2015 4:03 pm
- Forum: Building Installers
- Topic: prepending value to registry entry
- Replies: 4
- Views: 4720
- Jump to post
Re: prepending value to registry entry
An update on my question: after posting the question I noticed that selecting "prepend" changes the reg key type from REG_SZ to REG_MULTI_SZ. I think this is actually the root of the problem. The StencilPath and TemplatePath are Visio reg entries and Visio doesn't recognize the key after the type ...