Difference between revisions of "Windows"
Jump to navigation
Jump to search
(add a pair of ms-exchange related links) |
|||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
See Also: [[Fix-a-Fuckup]] | See Also: [[Fix-a-Fuckup]] | ||
| + | == PowerShell == | ||
| + | === Connecting Exchange Online 365 == | ||
| + | <pre> | ||
| + | PS C:\Users\kfarmer> Import-Module ExchangeOnlineManagement | ||
| + | PS C:\Users\kfarmer> Connect-ExchangeOnline -UserPrincipalName kfarmer@ | ||
| + | |||
| + | ---------------------------------------------------------------------------------------- | ||
| + | This V3 EXO PowerShell module contains new REST API backed Exchange Online cmdlets which doesn't require WinRM for Client-Server communication. You can now run these cmdlets after turning off WinRM Basic Auth in your client machine thus making it more secure. | ||
| + | |||
| + | Unlike the EXO* prefixed cmdlets, the cmdlets in this module support full functional parity with the RPS (V1) cmdlets. | ||
| + | |||
| + | V3 cmdlets in the downloaded module are resilient to transient failures, handling retries and throttling errors inherently. | ||
| + | |||
| + | REST backed EOP and SCC cmdlets are also available in the V3 module. Similar to EXO, the cmdlets can be run without WinRM basic auth enabled. | ||
| + | |||
| + | For more information check https://aka.ms/exov3-module | ||
| + | ---------------------------------------------------------------------------------------- | ||
| + | </pre> | ||
| + | |||
| + | === "tail -f" === | ||
| + | PS C:\> Get-Content somefile.log -Tail 5 -Wait | ||
== MS Exchange Server == | == MS Exchange Server == | ||
| Line 10: | Line 31: | ||
* [http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=98E45481-1458-4809-97D6-50D8AEEBD8A1&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f8%2fa%2f0%2f8a024b83-b003-47bd-b4dc-d4c46071d479%2fE2k3AdminGuide.doc Administration Guide for Exchange Server 2003] | * [http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=98E45481-1458-4809-97D6-50D8AEEBD8A1&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f8%2fa%2f0%2f8a024b83-b003-47bd-b4dc-d4c46071d479%2fE2k3AdminGuide.doc Administration Guide for Exchange Server 2003] | ||
* [http://www.microsoft.com/downloads/info.aspx?na=40&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=797E65CB-B07F-4F77-99A5-58D02EA963DA&u=http%3a%2f%2fgo.microsoft.com%2ffwlink%2f%3fLinkId%3d46437 Best Practices for Exchange Server Public Folders] | * [http://www.microsoft.com/downloads/info.aspx?na=40&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=797E65CB-B07F-4F77-99A5-58D02EA963DA&u=http%3a%2f%2fgo.microsoft.com%2ffwlink%2f%3fLinkId%3d46437 Best Practices for Exchange Server Public Folders] | ||
| + | |||
| + | |||
| + | == Troubleshooting Docs == | ||
| + | * [[Windows Printer BSOD KB5000802 and KB5000808 GPO Script]] | ||
| + | === WiFi (Wireless 802.11) === | ||
| + | * [http://technet.microsoft.com/en-us/library/bb457018.aspx http://technet.microsoft.com/en-us/library/bb457018.aspx] : A Support Guide for Wireless Diagnostics and Troubleshooting | ||
| + | |||
| + | Highlights: | ||
| + | |||
| + | Wireless logs. Logging can be enabled through the netsh ras set tracing * en command. After | ||
| + | enabling logging, you can either restart the computer or restart the Wireless Zero Configuration | ||
| + | (for Windows XP) or Wireless Configuration (for Windows Server 2003) service with the net stop | ||
| + | wzcsvc and net start wzcsvc commands. The wireless logs are located in the systemroot\tracing | ||
| + | folder. The log files most useful for troubleshooting wireless issues are the following: | ||
| + | |||
| + | Wzctrace.log Used mostly for 802.11 association. This file is present only on computers running | ||
| + | Windows XP Service Pack 2 (SP2) or Windows Server 2003 Service Pack 1. | ||
| + | |||
| + | Eapol.log Used mostly for IEEE 802.1X authentication. | ||
| + | |||
| + | Wzcdlg.log Used for user interface changes, such as changes made through the View Available | ||
| + | Networks or Choose a wireless network dialog boxes. | ||
| + | |||
| + | Netman.log Used for user interface changes. | ||
| + | |||
| + | Netshell.log Used for user interface changes. | ||
| + | |||
| + | Along with any .old versions of these files | ||
| + | |||
| + | There are additional (much deeper) details in the above-linked manual, including OID Key:Value translations for authentication mode, etc. Imagine that, visibility into a completely glued-shut OS! | ||
Latest revision as of 08:29, 13 November 2024
Random Documentation
See Also: Fix-a-Fuckup
PowerShell
= Connecting Exchange Online 365
PS C:\Users\kfarmer> Import-Module ExchangeOnlineManagement PS C:\Users\kfarmer> Connect-ExchangeOnline -UserPrincipalName kfarmer@ ---------------------------------------------------------------------------------------- This V3 EXO PowerShell module contains new REST API backed Exchange Online cmdlets which doesn't require WinRM for Client-Server communication. You can now run these cmdlets after turning off WinRM Basic Auth in your client machine thus making it more secure. Unlike the EXO* prefixed cmdlets, the cmdlets in this module support full functional parity with the RPS (V1) cmdlets. V3 cmdlets in the downloaded module are resilient to transient failures, handling retries and throttling errors inherently. REST backed EOP and SCC cmdlets are also available in the V3 module. Similar to EXO, the cmdlets can be run without WinRM basic auth enabled. For more information check https://aka.ms/exov3-module ----------------------------------------------------------------------------------------
"tail -f"
PS C:\> Get-Content somefile.log -Tail 5 -Wait
MS Exchange Server
Troubleshooting Docs
WiFi (Wireless 802.11)
- http://technet.microsoft.com/en-us/library/bb457018.aspx : A Support Guide for Wireless Diagnostics and Troubleshooting
Highlights:
Wireless logs. Logging can be enabled through the netsh ras set tracing * en command. After enabling logging, you can either restart the computer or restart the Wireless Zero Configuration (for Windows XP) or Wireless Configuration (for Windows Server 2003) service with the net stop wzcsvc and net start wzcsvc commands. The wireless logs are located in the systemroot\tracing folder. The log files most useful for troubleshooting wireless issues are the following: Wzctrace.log Used mostly for 802.11 association. This file is present only on computers running Windows XP Service Pack 2 (SP2) or Windows Server 2003 Service Pack 1. Eapol.log Used mostly for IEEE 802.1X authentication. Wzcdlg.log Used for user interface changes, such as changes made through the View Available Networks or Choose a wireless network dialog boxes. Netman.log Used for user interface changes. Netshell.log Used for user interface changes. Along with any .old versions of these files
There are additional (much deeper) details in the above-linked manual, including OID Key:Value translations for authentication mode, etc. Imagine that, visibility into a completely glued-shut OS!