<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>sysadmin &#8211; zaur.it</title>
	<atom:link href="https://zaur.it/tag/sysadmin/feed/" rel="self" type="application/rss+xml" />
	<link>https://zaur.it</link>
	<description>Practical tools and guides for system administrators</description>
	<lastBuildDate>Sun, 06 Sep 2026 08:20:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://zaur.it/wp-content/uploads/2025/04/cropped-LogoZaurIt-e1745511455393-1-32x32.png</url>
	<title>sysadmin &#8211; zaur.it</title>
	<link>https://zaur.it</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>powercfg on Windows: power plans, sleep diagnostics and battery reports</title>
		<link>https://zaur.it/powercfg-windows-power-plans-sleep-diagnostics/</link>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Sun, 06 Sep 2026 08:19:49 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[cmd]]></category>
		<category><![CDATA[power management]]></category>
		<category><![CDATA[powercfg]]></category>
		<category><![CDATA[sleep]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2582</guid>

					<description><![CDATA[powercfg.exe is the command-line front end for the Windows power subsystem. It reads and writes power plans, reports which sleep states the firmware actually offers, names the process that is keeping a machine awake, and generates the battery, energy and sleep-study reports that Control Panel never exposes. For a sysadmin the interesting part is not [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Test-NetConnection in Windows: the PowerShell replacement for ping, telnet and tracert</title>
		<link>https://zaur.it/test-netconnection-powershell-windows/</link>
					<comments>https://zaur.it/test-netconnection-powershell-windows/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Sat, 05 Sep 2026 08:18:48 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[network troubleshooting]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[ports]]></category>
		<category><![CDATA[powershell]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[Test-NetConnection]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2568</guid>

					<description><![CDATA[Test-NetConnection is the built-in PowerShell cmdlet that answers the three questions a sysadmin asks when something on the network stops working: can I reach the host at all, is the TCP port actually open, and which path does the traffic take. It ships with Windows in the NetTCPIP module, so there is nothing to install [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/test-netconnection-powershell-windows/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>net use in Windows: mapped drives, credentials and error 1219</title>
		<link>https://zaur.it/net-use-windows-mapped-drives/</link>
					<comments>https://zaur.it/net-use-windows-mapped-drives/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 22:41:19 +0000</pubDate>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[cmd]]></category>
		<category><![CDATA[net use]]></category>
		<category><![CDATA[network drive]]></category>
		<category><![CDATA[smb]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2546</guid>

					<description><![CDATA[net use maps a network share to a drive letter, lists what is already mapped, and disconnects it again. That part takes thirty seconds to learn. What takes years to learn is why the drive works for you and not for the service, why the same command fails with error 1219 on the second share, [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/net-use-windows-mapped-drives/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>chkdsk in Windows: what each switch does, and when not to run it</title>
		<link>https://zaur.it/chkdsk-windows-switches-online-scan/</link>
					<comments>https://zaur.it/chkdsk-windows-switches-online-scan/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 22:16:25 +0000</pubDate>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[chkdsk]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[ntfs]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2527</guid>

					<description><![CDATA[Most of what administrators know about chkdsk was true in 2005. Run it with /f /r, reboot, watch a progress percentage for four hours, hope. On a modern NTFS volume that ritual is usually the wrong move, and on a large disk it is an outage you chose to have. Since Windows 8 and Windows [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/chkdsk-windows-switches-online-scan/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>takeown in Windows: take ownership of files and folders safely</title>
		<link>https://zaur.it/takeown-windows-file-ownership/</link>
					<comments>https://zaur.it/takeown-windows-file-ownership/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 22:12:27 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[icacls]]></category>
		<category><![CDATA[NTFS permissions]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[takeown]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2522</guid>

					<description><![CDATA[Administrator rights do not grant access to a file. They grant the ability to take ownership of it, and ownership is what lets you rewrite the permissions. That distinction is the whole reason takeown exists, and it is why &#8220;I am an admin, why is this access denied&#8221; is such a common question. The usual [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/takeown-windows-file-ownership/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>klist in Windows: read and clear the Kerberos ticket cache</title>
		<link>https://zaur.it/klist-kerberos-ticket-cache-windows/</link>
					<comments>https://zaur.it/klist-kerberos-ticket-cache-windows/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 22:09:15 +0000</pubDate>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[active directory]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[kerberos]]></category>
		<category><![CDATA[klist]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2516</guid>

					<description><![CDATA[Kerberos fails quietly. When a ticket cannot be issued, Windows falls back to NTLM or simply returns access denied, and nothing on screen mentions Kerberos at all. klist is the one built-in tool that shows what the machine actually holds and what it asked for. It reads the Kerberos ticket cache of a logon session: [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/klist-kerberos-ticket-cache-windows/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>schtasks in Windows: create, query and audit scheduled tasks from CMD</title>
		<link>https://zaur.it/schtasks-windows-scheduled-tasks/</link>
					<comments>https://zaur.it/schtasks-windows-scheduled-tasks/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 21:58:49 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[automation]]></category>
		<category><![CDATA[cmd]]></category>
		<category><![CDATA[schtasks]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[task scheduler]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2483</guid>

					<description><![CDATA[schtasks is the command line interface to the Windows Task Scheduler. It creates, queries, runs, stops and deletes scheduled tasks, on the local machine or on a remote one, without opening the console. Everything the GUI can do, it can do, and a few things the GUI makes painful. The reason to learn it is [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/schtasks-windows-scheduled-tasks/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>w32tm in Windows: diagnose and fix domain time synchronisation</title>
		<link>https://zaur.it/w32tm-windows-time-synchronization/</link>
					<comments>https://zaur.it/w32tm-windows-time-synchronization/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 21:53:28 +0000</pubDate>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[active directory]]></category>
		<category><![CDATA[kerberos]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[time synchronization]]></category>
		<category><![CDATA[w32tm]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2477</guid>

					<description><![CDATA[w32tm is the command line front end to the Windows Time service. It reports where a machine gets its time, how far off it is, and whether the last synchronisation actually worked. On a standalone PC none of that matters much. In a domain it decides whether Kerberos issues tickets at all. Time problems rarely [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/w32tm-windows-time-synchronization/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>repadmin in Windows: check, read and force Active Directory replication</title>
		<link>https://zaur.it/repadmin-active-directory-replication/</link>
					<comments>https://zaur.it/repadmin-active-directory-replication/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 21:49:48 +0000</pubDate>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[active directory]]></category>
		<category><![CDATA[repadmin]]></category>
		<category><![CDATA[replication]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2475</guid>

					<description><![CDATA[repadmin is the tool that answers one question no GUI answers quickly: is every domain controller in this forest actually receiving the changes the others make? It reads replication metadata straight from AD DS, so it reports what the directory believes, not what a console has cached. Most administrators meet it during an incident. A [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/repadmin-active-directory-replication/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>sc Command in Windows: Query and Control Services from CMD</title>
		<link>https://zaur.it/sc-command-windows/</link>
					<comments>https://zaur.it/sc-command-windows/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 08:22:15 +0000</pubDate>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[cmd]]></category>
		<category><![CDATA[sc]]></category>
		<category><![CDATA[service control manager]]></category>
		<category><![CDATA[services]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[windows commands]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2252</guid>

					<description><![CDATA[How to use sc.exe to query, configure and control Windows services from the command line: start types, recovery actions, dependencies and remote servers.]]></description>
		
					<wfw:commentRss>https://zaur.it/sc-command-windows/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
