<?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>Uncategorized Archives - Wiredwolf Canada</title>
	<atom:link href="https://catastrophe.wiredwolf.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>https://catastrophe.wiredwolf.com/category/uncategorized/</link>
	<description></description>
	<lastBuildDate>Tue, 10 Aug 2021 02:03:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Exchange Services &#8211; Use PowerShell to restart</title>
		<link>https://catastrophe.wiredwolf.com/exchange-services-use-powershell-to-restart/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 21 Jul 2021 00:33:04 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://catastrophe.wiredwolf.com/?p=20967</guid>

					<description><![CDATA[<p>The newer generation Exchange, the more services there seem to be. Restarting them all manually is time consuming and unnecessary. Create a quick PS1 script and execute as Administrator: #Get List of Microsoft Exchange Services $services = Get-Service | ? { $_.name -like "MSExchange*" -and $_.Status -eq "Running"} #Restart each service foreach ($service in  [...]</p>
<p>The post <a href="https://catastrophe.wiredwolf.com/exchange-services-use-powershell-to-restart/">Exchange Services &#8211; Use PowerShell to restart</a> appeared first on <a href="https://catastrophe.wiredwolf.com">Wiredwolf Canada</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="fusion-fullwidth fullwidth-box fusion-builder-row-1 fusion-flex-container nonhundred-percent-fullwidth non-hundred-percent-height-scrolling" style="--awb-border-radius-top-left:0px;--awb-border-radius-top-right:0px;--awb-border-radius-bottom-right:0px;--awb-border-radius-bottom-left:0px;--awb-flex-wrap:wrap;" ><div class="fusion-builder-row fusion-row fusion-flex-align-items-flex-start fusion-flex-content-wrap" style="max-width:1144px;margin-left: calc(-4% / 2 );margin-right: calc(-4% / 2 );"><div class="fusion-layout-column fusion_builder_column fusion-builder-column-0 fusion_builder_column_1_1 1_1 fusion-flex-column" style="--awb-bg-size:cover;--awb-width-large:100%;--awb-margin-top-large:0px;--awb-spacing-right-large:1.92%;--awb-margin-bottom-large:0px;--awb-spacing-left-large:1.92%;--awb-width-medium:100%;--awb-spacing-right-medium:1.92%;--awb-spacing-left-medium:1.92%;--awb-width-small:100%;--awb-spacing-right-small:1.92%;--awb-spacing-left-small:1.92%;"><div class="fusion-column-wrapper fusion-flex-justify-content-flex-start fusion-content-layout-column"><div class="fusion-text fusion-text-1"><p>The newer generation Exchange, the more services there seem to be. Restarting them all manually is time consuming and unnecessary.</p>
<p>Create a quick PS1 script and execute as Administrator:</p>
<pre class="lang:ps decode:true ">#Get List of Microsoft Exchange Services
$services = Get-Service | ? 
 
#Restart each service
foreach ($service in $services)
</pre>
<p>It's quick and dirty but it does work. Better is to restart the services in the right sequence. Using this script I found that the "Microsoft Exchange Active Directory Topology" stops and takes down every service that's dependent, then starts them all back up again, then shuts most of the dependent services down again, restarting each. This adds quite a lot of time.</p>
<p>I'll rewrite this script to work more efficiently when I find the time.</p>
<p>Addendum – I did find the order in a blog in a Microsoft forum (for 2016)</p>
<ol>
<li>Microsoft Exchange Search Host</li>
<li>Microsoft Exchange Active Directory Topography</li>
<li>Microsoft Exchange Health Manager Recovery</li>
<li>Microsoft Exchange Anti-Spam Update</li>
<li>Microsoft Exchange Compliance Audit</li>
<li>Microsoft Exchange Search</li>
<li>Microsoft Exchange EdgeSync</li>
<li>Microsoft Exchange Mailbox Transport Delivery</li>
</ol>
<p>The remaining services can start in any order.</p>
</div></div></div></div></div>
<p>The post <a href="https://catastrophe.wiredwolf.com/exchange-services-use-powershell-to-restart/">Exchange Services &#8211; Use PowerShell to restart</a> appeared first on <a href="https://catastrophe.wiredwolf.com">Wiredwolf Canada</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Active Directory &#8211; Missing the Attribute Editor</title>
		<link>https://catastrophe.wiredwolf.com/active-directory-missing-the-attribute-editor/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 21 Jul 2021 00:26:13 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://catastrophe.wiredwolf.com/?p=20965</guid>

					<description><![CDATA[<p>If you've ever worked extensively with Exchange Online you know that your AD Attribute Editor is a must-have for setting SMTP addresses for synchronized accounts.  If it's missing (despite having already enabling Advanced Features) then you need to hack AD itself. Fortunately it's simple to fix this: Open ADSIEDIT.MSC Select Configuration as the naming context  [...]</p>
<p>The post <a href="https://catastrophe.wiredwolf.com/active-directory-missing-the-attribute-editor/">Active Directory &#8211; Missing the Attribute Editor</a> appeared first on <a href="https://catastrophe.wiredwolf.com">Wiredwolf Canada</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If you&#8217;ve ever worked extensively with Exchange Online you know that your AD Attribute Editor is a must-have for setting SMTP addresses for synchronized accounts.&nbsp; If it&#8217;s missing (despite having already enabling Advanced Features) then you need to hack AD itself.</p>
<p>Fortunately it&#8217;s simple to fix this:</p>
<ul>
<li>Open ADSIEDIT.MSC</li>
<li>Select Configuration as the naming context</li>
<li>Expand &#8211;&gt; CN=DisplaySpecifiers &#8211;&gt; CN=409 &#8211;&gt; CN=<strong>user-Display</strong></li>
<li>Double Click AdminPropertyPages</li>
<li>Add this value:
<ul>
<li>11,{c7436f12-a27f-4cab-aaca-2bd27ed1b773}</li>
<li>Click on OK</li>
</ul>
</li>
<li>Click on OK</li>
</ul>
<p>Done.&nbsp; Close AD Users &amp; Computers if it&#8217;s still open.&nbsp; Then open it back up and look for the Attributes on any given account.&nbsp; They should be there.</p>
<p>You can also update the Group-Display object so the Attribute Editor will appear for Groups as well.&nbsp; Note, the number prefix to the COM Class ID is the sequence number, so if the highest number in the list is 10, the next value is 11.&nbsp; If the highest number in the list is 6, then the prefix becomes 7.&nbsp;</p>
<ul>
<li>Open ADSIEDIT.MSC</li>
<li>Select Configuration as the naming context</li>
<li>Expand &#8211;&gt; CN=DisplaySpecifiers &#8211;&gt; CN=409 &#8211;&gt; CN=<strong>group-Display</strong></li>
<li>Double Click AdminPropertyPages</li>
<li>Add this value:
<ul>
<li>7,{88D2CF03-1BF2-465C-8173-C22AD02DDEDF}</li>
<li>Click on OK</li>
</ul>
</li>
<li>Click on OK</li>
</ul>
<p>The post <a href="https://catastrophe.wiredwolf.com/active-directory-missing-the-attribute-editor/">Active Directory &#8211; Missing the Attribute Editor</a> appeared first on <a href="https://catastrophe.wiredwolf.com">Wiredwolf Canada</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Azure AD Connect and Custom Attributes</title>
		<link>https://catastrophe.wiredwolf.com/azure-ad-connect-and-custom-attributes/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 08 Jun 2021 05:51:13 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://catastrophe.wiredwolf.com/?p=20962</guid>

					<description><![CDATA[<p>Azure AD Connect does a good job of linking your On Premises Active Directory to Azure AD.  But what if you want to do some customizations?  In a previous post I detailed how to set up a Dynamic Distribution Group in Exchange Online.  In the example provided I included a CustomAttribute1 field where I set  [...]</p>
<p>The post <a href="https://catastrophe.wiredwolf.com/azure-ad-connect-and-custom-attributes/">Azure AD Connect and Custom Attributes</a> appeared first on <a href="https://catastrophe.wiredwolf.com">Wiredwolf Canada</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Azure AD Connect does a good job of linking your On Premises Active Directory to Azure AD.&nbsp; But what if you want to do some customizations?&nbsp;</p>
<p>In a previous post I detailed how to set up a Dynamic Distribution Group in Exchange Online.&nbsp; In the example provided I included a CustomAttribute1 field where I set the group to filter out any CustomAttribute1 = &#8220;NoMember&#8221;.&nbsp; Read that post here:&nbsp; <a href="https://catastrophe.wiredwolf.com/dynamic-distribution-lists/">https://catastrophe.wiredwolf.com/dynamic-distribution-lists/</a></p>
<p>By default, though, Active Directory does not have these attribute options assigned to the users, or indeed anywhere in the Schema.&nbsp; You have to add them by extending the AD Schema.</p>
<p>The simplest way to do this is by downloading Exchange 2016/2019 CU (<a href="https://buildnumbers.wordpress.com/exchange/">latest</a>) &#8211; mounting the ISO &#8211; and executing the command:&nbsp;</p>
<blockquote><p>\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareSchema</p></blockquote>
<p>This is a little bit of a pain in the ass as the file is huge (5+ GB) to run a simple command without actually installing Exchange to your environment.&nbsp; However, a necessary time expense if you want to use these features.</p>
<p><em>Please note &#8211; CustomAttribute1-15 is not the same as msDS-cloudExtensionAttribute1-15.&nbsp; Do not use msDS-cloudExtensionAttribute.</em></p>
<p>Once you have your Schema extended with Exchange, the next step is to update/refresh your Azure AD Connector.</p>
<p>Open Azure AD Connect configuration and select Refresh Directory Schema.&nbsp; Run through the wizard, provide your Global Admin credentials, and complete the process.</p>
<p>Next, reopen Azure AD Connect configuration and this time Customize Synchronization Options.&nbsp; Click through, provide your Global Admin credentials where required, until you get to Optional Features.&nbsp; To this point you&#8217;ve probably only ever enabled Password Hash Synchronization but here&#8217;s where you enable other goodies such as Directory Extension Attribute Sync.&nbsp;&nbsp;</p>
<p>When Directory Extension Attribute Sync is enabled you&#8217;ll click through until you get to Directory Extensions.&nbsp; Scroll down through the available extensions and add all the ExtensionCustomAttribute1-15 for both Group and User to the right side.&nbsp; When they&#8217;re all selected, click on Next, then Configure, and wait until the wizard is completed and a new sync is initiated.</p>
<p>At this point you can now synchronize CustomAttribute1 through 15 from the Attributes section of your AD user.&nbsp;&nbsp;</p>
<p>The post <a href="https://catastrophe.wiredwolf.com/azure-ad-connect-and-custom-attributes/">Azure AD Connect and Custom Attributes</a> appeared first on <a href="https://catastrophe.wiredwolf.com">Wiredwolf Canada</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Office 365 and Common PowerShell Commands</title>
		<link>https://catastrophe.wiredwolf.com/office-365-and-common-powershell-commands/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 17 Feb 2021 03:19:12 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://catastrophe.wiredwolf.com/?p=20946</guid>

					<description><![CDATA[<p>I work with Exchange Online and Azure AD quite a lot and I'm constantly looking up the same commands to do simple things. This is a cheat-sheet of the common commands so I don't have to keep looking them up: Searching for the owner of a mailbox: There are a number of ways to  [...]</p>
<p>The post <a href="https://catastrophe.wiredwolf.com/office-365-and-common-powershell-commands/">Office 365 and Common PowerShell Commands</a> appeared first on <a href="https://catastrophe.wiredwolf.com">Wiredwolf Canada</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="fusion-fullwidth fullwidth-box fusion-builder-row-2 fusion-flex-container nonhundred-percent-fullwidth non-hundred-percent-height-scrolling" style="--awb-border-radius-top-left:0px;--awb-border-radius-top-right:0px;--awb-border-radius-bottom-right:0px;--awb-border-radius-bottom-left:0px;--awb-flex-wrap:wrap;" ><div class="fusion-builder-row fusion-row fusion-flex-align-items-flex-start fusion-flex-content-wrap" style="max-width:1144px;margin-left: calc(-4% / 2 );margin-right: calc(-4% / 2 );"><div class="fusion-layout-column fusion_builder_column fusion-builder-column-1 fusion_builder_column_1_1 1_1 fusion-flex-column" style="--awb-bg-size:cover;--awb-width-large:100%;--awb-margin-top-large:0px;--awb-spacing-right-large:1.92%;--awb-margin-bottom-large:0px;--awb-spacing-left-large:1.92%;--awb-width-medium:100%;--awb-spacing-right-medium:1.92%;--awb-spacing-left-medium:1.92%;--awb-width-small:100%;--awb-spacing-right-small:1.92%;--awb-spacing-left-small:1.92%;"><div class="fusion-column-wrapper fusion-flex-justify-content-flex-start fusion-content-layout-column"><div class="fusion-text fusion-text-2"><p>I work with Exchange Online and Azure AD quite a lot and I'm constantly looking up the same commands to do simple things.</p>
<p>This is a cheat-sheet of the common commands so I don't have to keep looking them up:</p>
<p>Searching for the owner of a mailbox:</p>
<p>There are a number of ways to do this but this is the most reliable one</p>
<blockquote>
<p>Get-Mailbox -IncludeInactiveMailbox -Identity * | Where-Object <span class="enlighter-g1"></span> <span class="enlighter-g0">| </span>Format-List Identity, EmailAddresses</p>
</blockquote>
<p>Finding Inbox-Rules</p>
<blockquote>
<p>Get-InboxRule -mailbox 'info@domain.com' | select Name,Description</p>
</blockquote>
<p>Removing Inbox-Rules (en masse)</p>
<blockquote>
<p>Get-InboxRule -mailbox 'info@domain.com' | Remove-InboxRule</p>
</blockquote>
<p>Find out if any accounts in the tenant have mail forwarding:</p>
<div class="">
<blockquote>
<div><span class="enlighter-text">Get-Mailbox -ResultSize Unlimited </span><span class="enlighter-g0">| </span><span class="enlighter-text">Where </span><span class="enlighter-g1"></span> <span class="enlighter-g0">| </span>Select Name, ForwardingAddress, ForwardingsmtpAddress, DeliverToMailboxAndForward</div>
</blockquote>
<div>Removing a forwarder:</div>
</div>
<blockquote>
<div><span class="enlighter-text">Set-Mailbox <i>user@domain.com </i>-ForwardingAddress $</span><span class="enlighter-k1">NULL</span><span class="enlighter-text"> -ForwardingSmtpAddress $NULL</span></div>
</blockquote>
<div>Exchange Message Trace:</div>
<blockquote>
<div>Get-TransportServer | Get-MessageTrackingLog -ResultSize Unlimited -Start "mm/dd/yyyy 00:00:00 AM" -End "mm/dd/yyyy 00:00:00 AM" -Sender someone@domain.com | Select , , * | Export-Csv D:ReportsSent_Nuno.csv <em>–</em>NoTypeInformation</div>
</blockquote>
<div>You can leave -Sender someone@domain.com out if you want to. Also, note the date format is MONTH/DAY/YEAR. This is critical.</div>
<p>Another helpful thing I found – a lot of queries in Exchange Online truncates the output so you end up with </p>
<p>If that happens there are two ways to address it:</p>
<ol>
<li>Pipe the output to FT or FL with -Wrap -Autosize</li>
<li>Set the $formatEnumerationLimit: $FormatEnumerationLimit =-1</li>
</ol>
<hr>
<p>I'll update this list on a regular basis moving forward.</p>
</div></div></div></div></div>
<p>The post <a href="https://catastrophe.wiredwolf.com/office-365-and-common-powershell-commands/">Office 365 and Common PowerShell Commands</a> appeared first on <a href="https://catastrophe.wiredwolf.com">Wiredwolf Canada</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
