Przełącznik języka
Zaproś mnie na KAWE
Jeżeli podoba Ci się strona i chcesz wspomóc projekt!
Tools
Mining
Księgowość
Płatnik
Security
CMS
Hardware
Backup
Windows Server
Uncategorised
Databases
Przydatne strony
Emulators
Poczta
PHP
Powershell
Storage Array
Active Directory
SEO
Serwis
MSSQL
DNS
Windows
Poradniki
Antivirus program
Linux
Naprawy
Windows Server
Foto
Licznik
Visitor Info
- IP: 18.216.172.229
- Browser: Unknown
- Browser Version:
- Operating System: Unknown
Who Is Online
Configure RDS Collections Using PowerShell
Create a new collection
Open a PowerShell prompt from the taskbar or Start menu, and then use the New-RDSessionCollection cmdlet to create a new collection.
In the example below, I’ve given the collection a name, a description, and specified the RDS Session Host and Connection Broker servers using their fully qualified domain names (FQDNs)
Example:
New-RDSessionCollection –CollectionName MultiTS –SessionHost TS1.net.lan –CollectionDescription ‘TS’ –ConnectionBroker TS1.net.lan
To verify the creation of the new collection,
use the Get-RDSessionCollection cmdlet, replacing TS1.net.lan with the name of your RDS Connection Broker. Get-RDSessionCollection –ConnectionBroker TS1.net.lan
To remove a collection from an RDS Connection Broker,
use the Remove-RDSessionCollection cmdlet as shown here, again replacing the values for -CollectionName and -ConnectionBroker as needed for your environment.
Remove-RDRemoteApp -Alias TS02 -CollectionName PetriRemoteApps -ConnectionBroker TS1.net.lan
ESXi Log File Locations
ESXi records host activity in log files, using a syslog facility.
| Component | Location | Purpose |
|---|---|---|
| Authentication | /var/log/auth.log | Contains all events related to authentication for the local system. |
| ESXi host agent log | /var/log/hostd.log | Contains information about the agent that manages and configures the ESXi host and its virtual machines. |
| Shell log | /var/log/shell.log | Contains a record of all commands typed into the ESXi Shell and shell events (for example, when the shell was enabled). |
| System messages | /var/log/syslog.log | Contains all general log messages and can be used for troubleshooting. This information was formerly located in the messages log file. |
| vCenter Server agent log | /var/log/vpxa.log | Contains information about the agent that communicates with vCenter Server (if the host is managed by vCenter Server). |
| Virtual machines | The same directory as the affected virtual machine's configuration files, named vmware.log and vmware*.log. For example, /vmfs/volumes/datastore/virtual machine/vwmare.log | Contains virtual machine power events, system failure information, tools status and activity, time sync, virtual hardware changes, vMotion migrations, machine clones, and so on. |
| VMkernel | /var/log/vmkernel.log | Records activities related to virtual machines and ESXi. |
| VMkernel summary | /var/log/vmksummary.log | Used to determine uptime and availability statistics for ESXi (comma separated). |
| VMkernel warnings | /var/log/vmkwarning.log | Records activities related to virtual machines. |
| Quick Boot | /var/log/loadESX.log | Contains all events related to restarting an ESXi host through Quick Boot. |
| Trusted infrastructure agent | /var/run/log/kmxa.log | Records activities related to the Client Service on the ESXi Trusted Host. |
| Key Provider Service | /var/run/log/kmxd.log | Records activities related to the vSphere Trust Authority Key Provider Service. |
| Attestation Service | /var/run/log/attestd.log | Records activities related to the vSphere Trust Authority Attestation Service. |
| ESX Token Service | /var/run/log/esxtokend.log | Records activities related to the vSphere Trust Authority ESX Token Service. |
| ESX API Forwarder | /var/run/log/esxapiadapter.log | Records activities related to the vSphere Trust Authority API forwarder. |
Source
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-D0D77526-65DC-4D08-A52F-51D5B0DAF8C3.html
Windows Update KB5018410 fails to install Windows 10 version 21H2
Windows Update KB5018410 fails to install Windows 10 version 21H2
Microsoft recently released Windows 10 Build 19044.2130 with KB5018410 Update for Devices running Windows 10 November 2021 update with various security fixes. But it appears to be causing headaches for users.
Unfortunately, some users report a lot of problems.
Some report that KB5018410 for Windows 10 version 21H2 broke some PCs.
Some others 2022-10 Cumulative update for windows 10 version 21H2 for x64 based system (KB5018410) failed to install with different errors 0x800f0922, 0x800f0826 and more.
There are also problems with the work of the explorer that hangs.
The taskbar also stops working and starts flashing.
Computer has become slower.
Windows crashes with a blue screen (BSOD) and reboots.
Windows explorer crashes or freezes.
The taskbar icons do not appear.
Also, system users mentioned on the Microosft forums as the windows 10 KB5018410 upsate was downloaded but stuck while installing these updates.
Here's a list of all bug fixes:
-
Addresses an issue that requires you to reinstall an app if you did not get the app from the Microsoft Store. This issue occurs after you upgrade to Windows 10 or a newer OS.
-
Addresses a rare error that leads to a blue screen. This occurs after you change the display mode while you are using more than one display.
-
Addresses an issue that forces the IE mode tabs in a session to reload.
-
Addresses an issue that affects IE mode after you open a PDF file. When you try to open a different page using the same browser window, the page will not open in that browser window.
-
Addresses an issue that affects the Microsoft Japanese IME when it is active and the IME mode is on. When you use the numeric keypad to insert a dash (-) character, the IME inserts the wrong one.
-
Addresses an issue that affects the rendering of the search box. It does not render properly if you sign in using Tablet mode.
-
Addresses a known issue that affects daylight saving time in Chile. This issue might affect the time and dates used for meetings, apps, tasks, services, transactions, and more.
Last but not the least, the update contains miscellaneous security improvements to internal OS functionality, as per Microsoft's security documentation.
How to fix: Windows 10 issues after installing KB5018410 update.
Step 1. Uninstall KB5018410 update.
Proceed and remove the KB5018410 update
Step 2. Install KB5020435 Update.
1. Navigate to Microsoft Update Catalog website and download the KB5020435 update according your Windows 10 version.
How to clear the YUM cache
How to clear the YUM cache
What is yum?
The Yellowdog Updater, Modified (yum) is an open-source command-line package-management utility for Linux operating systems using the RPM Package Manager. Yum allows automatic updates, package and dependency management, on RPM-based distributions. Like the Advanced Packaging Tool (APT)
How to clear the yum cache:
When a package is downloaded, installed and is removed there is a chance that the package may still be saved/stored in the yum’s cache. So to clean all the cached packages from the enabled repository cache directory, login as root and execute the following:
#yum clean packages
To purge the old package headers information completely, execute the execute the command below:
#yum clean headers
To clean metadata for each enabled repository, execute the command below:
#yum clean metadata
If you wish to clean all the cached files from any enabled repository at once, execute the command:
#yum clean all