Activclient Windows 11

0 views

Skip to first unread message

Smacka Shock

unread,

Aug 3, 2024, 11:12:34 AM8/3/24

to fortofurtka

I am new to Action scripts and attempting to create an Uninstall for Active Client software. I am attempting to mimic a popular Winscp uninstall action script because I need to uninstall multiple versions of the software. The problem is that although the software is there, it keeps coming up false in the Fixlet Debugger when searching for the app and uninstall string. Once that happens the uninstall does not take place. Here is what I am using. Any help would be greatly appreciated.

One thing you may trip on is that ActivClient is a native (ie 64-bit) application, while the BigFix Client itself is 32-bit. You have to make a couple of considerations, like querying native registry in the Relevance and disabling 32-bit redirection in the Action Script.

Relevance:
windows of operating system AND if exists property "in proxy agent context" then not in proxy agent context else true AND exists keys whose (value "DisplayName" of it as string starts with "ActivClient") of keys "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" of native registry

Hello @Strawgate, and @JasonWalker A thank you is long over due. Thanks for pointing out why my first attempt failed, creating the correct script and breaking it down. It really helped the way you explained each step. @JasonWalker thanks for your input as well. I like the idea of using the appendfile command to create, move, and install the software package. I am testing the two methods as we speak to see which works best for my environment.
Thank you both. I will keep you posted.

I am an admin, and attempting to disable "Windows Hello for Business" also referred to as 2-step authentication. From what I gather, this option is set as "disabled" by default. I confirmed this. However Whenever I join a device to Azure AD, it is always prompted with "Windows Hello" and to create a pin. Where can I find the option that allows me to disable this?

The idea is solid, but as with virtually all of the recent 365 'improvements' turned on by default (clutter, focussed inbox etc) they're being foisted on users that don't need them, they are tricky if not impossible to remove, and just generate support issues needlessly.

I also strongly recomend disabling it for now. But it is possible to use hello and a local nas although it is not recomended... you need to change login alternative and choose other user and log in by that was but it is much more inconvinient than just not using Hello.

@ErikROsberg There is no need for extra local accounts if you use a NAS. Just make a network connection to your NAS and save it as you connect. That way the credentials will be stored in the Windows Credential Manager (press "start" and type "credential manager" to launch it). You can then easily logon to windows using Windows Hello and the link to your NAS will just work on the basis of your stored password.

@James King This is definitely still happening. Any network drive will not be able to be accessed if using Windows Hello. It will say "A specified logon session does not exist. It may have already been terminated."

Why do they do this? When they do **bleep** like this I honestly feel like signing every single microsoft center up to scientology, jehovas witnesses, other various spam packages and see how they like being bombarded with CRAP noone asked for. F*** OFF!

My problem with it is that it's invasive. At no point are you asked if you want to activate it and there's no obvious way to disable it. I could probably disable it if I had the time, but for gods sake. Why force it upon people without asking? It's dirty practices and deserves to be spat on.

@James King
You are absolutely correct. Same deal, a NAS is blocked for the only user of 3 AD-Joined systems who uses the Hello PIN. When that single user logs in w/ regular password, NAS access is fine.

@Thierry Vos
They use their AzureAD joined email address & password to connect to the NAS share (which was shared for Public/Everyone on the NAS side). Tell user to choose the "Key" icon at login (Other logon options) and use those creds, and they're all fine.

Tried hacking the Registry for the Hello PIN, since MS disables your ability to change it when AzureAD joined...unless you pay for a certain Tier (or Add-on) within Azure itself. No go...Registry hack didn't help. So if you created/chose the option to use a Hello PIN when joining the workstation to Azure, you're stuck w/ the OPTION.

This is Azure's habit, you pay for this, you pay for that, you subscribe for this, you subscribe for that, for more of that, for ability to do that, etc.. It's not my preference, over a local Domain w/ local Domain AD joined computers being the standard and long term (long term) cost savings.

Disclaimer: The registry is a database in Windows that contains important information about system hardware, installed programs and settings, and profiles of each of the user accounts on the computer. Windows often reads and updates the information in the registry.

Normally, software programs make registry changes automatically. You should not make unnecessary changes to the registry. Changing registry files incorrectly can cause Windows to stop working or make Windows report the wrong information.

@RyanRoe I feel your pain! I have exactly the same issue. I've tried everything I can think of and I can find on the interwebs including multiple points in the network connection chain...with two separate computers (one a laptop and one a desktop). I had the network all talking nicely to each other as well as the NAS drive for awhile but then I made the mistake of a WIndows 10 update. Still trying to recover...

As an aside to previous comments on the subject, Synology (one of the two main NAS drive manufacturers) told me via a technical support enquiry that they do not support Windows Hello installations. I generated this enquiry while trying to attach a brand new DiskStation NAS (26 June 2020) to my network.