There's a known issue when attempting to configure a network adapter to set a static IP address through SConfig on a freshly installed Windows Server 2022 Core. Upon attempting to configure the IP address, it will fail with the following error message:
Setting NIC to static IP...
Failed to release DHCP lease.
Result code: 83
Method name: ReleaseDHCPLease
You can manually work around the issue by configuring the IP address using Powershell directly:
First, list all network adapters present to find the correct one:Get-NetAdapter
You can reference by Name (InterfaceAlias) or by ifIndex (InterfaceIndex).
Next, remove any existing (APIPA) addresses:Remove-NetIPAddress -InterfaceAlias ...
There are several ways of booting a Windows system into Safe Mode. But if you're no longer able to boot into the system to turn on Safe Mode, and the system doesn't automatically boot into safe mode, you're usually only left with a single option: using a Windows Installer USB or DVD/ISO to enable Safe Mode.
To accomodate this, you'll need a bootable USB-key, DVD or ISO image (if you're running a VM).
Start up the system, booting from the bootable media. Because you already have Windows installed, you will need to hit Enter in time to boot from the bootable media.
When Windows Setup has started and the button "Install now" appears, click on the Repair your computer link at the bo ...
To troubleshoot issues with DNS dynamic updates (e.g., certain Active Directory-joined Windows servers not properly registering their hostnames in DNS), there's an easy way to troubleshoot via the DNS Server's audit log, where DNS updates are logged. To properly filter the log for certain IP addresses or hostnames, you'll need to use custom XML filters to properly filter on the contents of the log entries because of the way the events are logged and standard filters don't provide the proper filtering.
The audit log can be found in the Event Viewer at Applications and Services logs → Microsoft → Windows → DNS-Server → Audit. Once the log is open, click on Action → Fi ...
In VMware Horizon View VDI, when using floating pools with instant clones, you may run across a problem where VMs get the "Already Used" status after users log off. The VM remains unavailable for further use and does not get deleted or refreshed.
The reason for this usually is that some process is blocking the refresh/delete operation, causing the VM to remain unusable and powered on to allow a system administrator to investigate the issue. If this is not desired (e.g., the reason for the blockage is known but cannot be resolved immediately), there is a policy which can be set to allow for automatic clean up of these "dirty" VMs.
In an organization you may not want to get prompts to try out the new Outlook Preview versions. Luckily, there's a way to turn this off, either through GPO or through a registry key, which can be distributed to your users.
If you're using the latest Administrative Templates for Office, you can find the setting under User Configuration\Policies\Administrative Templates\Microsoft Outlook 2016\Outlook Options\Other, where you can enable the Disable Preview Place setting.
I recently ran into an issue during a full restore of a Time Machine backup where the Launchpad layout would not be restored, and instead returned to a default layout. If you're like me and have put a lot of effort in customizing the layout, it's a bummer having to do all the work again, especially since one would expect a full restore from Time Machine actually restores *everything* (but that's discussion for another thread, I guess).
At first, I assumed Time Machine didn't back up everything but, as it turns out, the files are present but not restored during a full restore operation. Luckily, there's a way recover this manually. You can also do this if for some reason Launchpad is corrupt ...
I recently ran into an issue where my FortiClient app on macOS no longer worked and I had to reinstall it. Unfortunately, if the installer detects it is already installed, it refuses to install and instead, simply attempts to update it, concludes there's no new version, and ends with the message "No updates found". The official solution is to use the FortiClient Uninstaller app, which can also be found in the /Applications, but if that's no option, you're seemingly stuck.
Fortunately, there's an easy way out by manually removing the app files, then rerunning the installer.
First, using Finder, completely remove the following apps (remove and remove from Bin):
When installing Powershell modules from the gallery, you may run into the following error, particularly on older versions of Windows (even Windows 10):
PS C:\WINDOWS\system32> Install-Module -Scope AllUsers -Name module-nameWARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2/'.PackageManagement\Install-Package : No match was found for the specified search criteria and module name 'module-name'. Try Get-PSRepository to see all available registered module repositories.
The most common reason for this (aside of having some other issue with internet access) is that Powershell may still be using TLS 1.0, which is no longer supported by Powershell Gallery.