How do I create a new instance without scaling? For example, I have 2 instances (which was my minimum number of instance) running in my scale set and I set up the scaling upto 100 instances. Can I create/start a new instance manually without triggering a scaling?
Pretty sure that’s just a way to force everyone to a higher Defender license in Azure. If every other AV product can have Tamper Protection with a simple password and control through some form of management tool, it seems hypocritical that the one they supply cannot be managed through Group Policy.
Well, Onedrive should be a decision for later. Many installers do not realise this will sync files. This is a major security risk for professionals if sensitive files are being duplicated. It also breaks scripts that expect a normal path for folders.. Now we have people with 30 or 40 dummy Microsoft accounts….
You can also add an account later. The major problem is that rather than basing the home folder on the user name (Mary, John, etc.) it is based on a substring of the logon, which is a bugger to remember for RDP.
You almost never logon with the Microsoft account, it will be a device PIN. Only networking and terminal services will use that logon. Again, you guess what it is and where it truncated.
Is the user account on the CISCO device you are using have level 15 privileges? Since the error seems to be the show run command it might be the user account does not have the correct privilege to execute the show run command?
Who wants to use a GUI if you can let handly Ansible all of it and you can just leave it all for automation… GUIs are outdated….
With Ansible you can automate you’re entire IT!
e.g. with an Ansible play you take a VM, check for updates, if available you set monitoring to pause that system, then you create a VM-snap, then you update, then you reboot and finally you email out a report and activate monitoring again… and you can do a lot of this even with your firewall (palo alto e.g.) and cisco devices. If things are changed you can have ansible change it back to keep a good state… try that with WSUS….
I’ve used `cat` and `>>` to add the contents of the public key file to administrators_authorized_keys file but the contents were converted on the fly to utf16. The file looked ok in notepad but openssh could not read it. What is worse: there was no error in the logs neither on server side nor in client (`-vvv`). I’ve wasted hours on this! I’ve tried `LogLevel DEBUG` in `sshd_config` but the `__PROGRAMDATA__/ssh/logs` directory is empty.
I have used the Autoruns to delete or disable applications sparingly. Like many Sysinternals apps, it is somewhat forbidding to the average user like myself, with its many settings and functions (but useful). There are manuals which document Sysinternals, which I have, but rarely read. They are probably out of date with the many changes made to Sysinternals. Good article.