Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.servervitalsigns.com/feed/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. >
  9.  
  10. <channel>
  11. <title>VitalSigns and PowerScripts Blog</title>
  12. <atom:link href="http://www.servervitalsigns.com/feed/" rel="self" type="application/rss+xml" />
  13. <link>http://www.servervitalsigns.com/</link>
  14. <description>Occastional musing from the developers of VitalSigns and PowerScripts -- the safe way to run PowerShell in the enterprise</description>
  15. <lastBuildDate>Tue, 23 May 2023 13:42:51 +0000</lastBuildDate>
  16. <language>en-US</language>
  17. <sy:updatePeriod>
  18. hourly </sy:updatePeriod>
  19. <sy:updateFrequency>
  20. 1 </sy:updateFrequency>
  21. <generator>https://wordpress.org/?v=6.4.3</generator>
  22. <item>
  23. <title>Assigning Licenses</title>
  24. <link>http://www.servervitalsigns.com/assigning-licenses/</link>
  25. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  26. <pubDate>Tue, 23 May 2023 13:36:04 +0000</pubDate>
  27. <category><![CDATA[PowerScripts]]></category>
  28. <category><![CDATA[PowerShell]]></category>
  29. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1284</guid>
  30.  
  31. <description><![CDATA[<p><img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2021/12/powershell-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" />We recently concluded development for a script for one of our clients who assigns dozens of E3 licenses per week. The challenge was that not all the products included in the E3 license was supported internally by the company. This meant that every license assigned also had to be tweaked in portal.azure.com to turn off [&#8230;]</p>
  32. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/assigning-licenses/">Assigning Licenses</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  33. ]]></description>
  34. <content:encoded><![CDATA[<img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2021/12/powershell-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />
  35. <p>We recently concluded development for a script for one of our clients who assigns dozens of E3 licenses per week. The challenge was that not all the products included in the E3 license was supported internally by the company.</p>
  36.  
  37.  
  38.  
  39. <p>This meant that every license assigned also had to be tweaked in portal.azure.com to turn off a number of products associated with each license.</p>
  40.  
  41.  
  42.  
  43. <figure class="wp-block-image size-full"><a href="http://www.servervitalsigns.com/wp-content/uploads/2023/05/image.png"><img fetchpriority="high" decoding="async" width="750" height="1024" src="http://www.servervitalsigns.com/wp-content/uploads/2023/05/image.png" alt="" class="wp-image-1285" srcset="http://www.servervitalsigns.com/wp-content/uploads/2023/05/image.png 750w, http://www.servervitalsigns.com/wp-content/uploads/2023/05/image-220x300.png 220w" sizes="(max-width: 750px) 100vw, 750px" /></a></figure>
  44.  
  45.  
  46.  
  47. <p>This entire process is easily scripted via PowerShell, and once validated we converted the script into a <a href="https://powerscripts365.com/">PowerScript</a> and pushed it down to the Service Desk. Now the Service Desk can assign licenses with ZERO training and ZERO mistakes.</p>
  48.  
  49.  
  50.  
  51. <p>We decided to include the script in the product so other people can use it as a starting point for their own license assignment script. The script content follows but what makes it interesting is the fact that it also turns off some of the features associated with the license. This was important to the client as the E3 license included software (“Microsoft Stream”) which the company did not want to support. The script also presents the user with a list of licenses to select from, as shown below:</p>
  52.  
  53.  
  54.  
  55. <figure class="wp-block-image size-full"><a href="http://www.servervitalsigns.com/wp-content/uploads/2023/05/image-1.png"><img decoding="async" width="1024" height="565" src="http://www.servervitalsigns.com/wp-content/uploads/2023/05/image-1.png" alt="" class="wp-image-1286" srcset="http://www.servervitalsigns.com/wp-content/uploads/2023/05/image-1.png 1024w, http://www.servervitalsigns.com/wp-content/uploads/2023/05/image-1-300x166.png 300w, http://www.servervitalsigns.com/wp-content/uploads/2023/05/image-1-768x424.png 768w" sizes="(max-width: 1024px) 100vw, 1024px" /></a></figure>
  56.  
  57.  
  58.  
  59. <p>For those curious, here is the script itself:</p>
  60.  
  61.  
  62.  
  63. <pre class="wp-block-code"><code>param(
  64.    &#91;AutoPopulate(ObjectType='users', MappedField='user_principal_name')]
  65.    &#91;string]$UserPrincipalName,
  66.  
  67.    &#91;ValidateSet('Stream', 'Developer Pack','Windows Store','Flow','Power BI','Business Essentials')]
  68.    &#91;string] $License
  69. )
  70.  
  71. try {
  72.  
  73.    $LicenseObjectArray = @(
  74.        &#91;PSCustomObject]@{
  75.            FriendlyName = 'Stream'
  76.            SkuPartNumber = 'STREAM'
  77.            DisabledPlanNames = @('Microsoft Stream')   # There are multiple plans in a license.
  78.                                                        # This will disable the 'Microsoft Stream' plan inside this license
  79.        },
  80.        &#91;PSCustomObject]@{
  81.            FriendlyName = 'Developer Pack'
  82.            SkuPartNumber = 'DEVELOPERPACK'
  83.            DisabledPlanIds = @()                       # Leave this empty to disable no plans
  84.        },
  85.        &#91;PSCustomObject]@{
  86.            FriendlyName = 'Windows Store'
  87.            SkuPartNumber = 'WINDOWS_STORE'
  88.            DisabledPlanNames = @()
  89.        },
  90.        &#91;PSCustomObject]@{
  91.            FriendlyName = 'Flow'
  92.            SkuPartNumber = 'FLOW_FREE'
  93.            DisabledPlanNames = @()
  94.        },
  95.        &#91;PSCustomObject]@{
  96.            FriendlyName = 'Power BI'
  97.            SkuPartNumber = 'POWER_BI_STANDARD'
  98.            DisabledPlanNames = @()
  99.        },
  100.        &#91;PSCustomObject]@{
  101.            FriendlyName = 'Business Essentials'
  102.            SkuPartNumber = 'O365_BUSINESS_ESSENTIALS'
  103.            DisabledPlanNames = @()
  104.        }
  105.    )
  106.  
  107.    $LicenseObject = $LicenseObjectArray | ? { $_.FriendlyName -eq $License }
  108.  
  109.    if(-not $LicenseObject) {
  110.        Write-Output 'License is not supported'
  111.        return
  112.    }
  113.  
  114.    $sku = Get-MgSubscribedSku -All -ErrorAction Stop | Where { $_.SkuPartNumber -eq $LicenseObject.SkuPartNumber }
  115.  
  116.    $disabledPlans = $sku.ServicePlans |  Where { $_.ServicePlanName -in $LicenseObject.DisabledPlanNames } | Select -ExpandProperty ServicePlanId
  117.  
  118.    if(-not $disabledPlans) { $disabledPlans = @()}
  119.    
  120.    $addLicenses = @(
  121.        @{
  122.            SkuId = $sku.SkuId
  123.            DisabledPlans = $disabledPlans
  124.        }
  125.    )
  126.  
  127.    Set-MgUserLicense -UserId $UserPrincipalName -AddLicenses $addLicenses -RemoveLicenses @() -ErrorAction Stop | Out-Null
  128.  
  129.    Write-Output "Successfully assigned the license $License to the user $UserPrincipalName"
  130. } catch {
  131.    Write-Output "Error while executing the script"
  132.    Write-Error $_
  133. }
  134. param(
  135.    &#91;AutoPopulate(ObjectType='users', MappedField='user_principal_name')]
  136.    &#91;string]$UserPrincipalName,
  137.  
  138.    &#91;ValidateSet('Stream', 'Developer Pack','Windows Store','Flow','Power BI','Business Essentials')]
  139.    &#91;string] $License
  140. )
  141.  
  142. try {
  143.  
  144.    $LicenseObjectArray = @(
  145.        &#91;PSCustomObject]@{
  146.            FriendlyName = 'Stream'
  147.            SkuPartNumber = 'STREAM'
  148.            DisabledPlanNames = @('Microsoft Stream')   # There are multiple plans in a license.
  149.                                                        # This will disable the 'Microsoft Stream' plan inside this license
  150.        },
  151.        &#91;PSCustomObject]@{
  152.            FriendlyName = 'Developer Pack'
  153.            SkuPartNumber = 'DEVELOPERPACK'
  154.            DisabledPlanIds = @()                       # Leave this empty to disable no plans
  155.        },
  156.        &#91;PSCustomObject]@{
  157.            FriendlyName = 'Windows Store'
  158.            SkuPartNumber = 'WINDOWS_STORE'
  159.            DisabledPlanNames = @()
  160.        },
  161.        &#91;PSCustomObject]@{
  162.            FriendlyName = 'Flow'
  163.            SkuPartNumber = 'FLOW_FREE'
  164.            DisabledPlanNames = @()
  165.        },
  166.        &#91;PSCustomObject]@{
  167.            FriendlyName = 'Power BI'
  168.            SkuPartNumber = 'POWER_BI_STANDARD'
  169.            DisabledPlanNames = @()
  170.        },
  171.        &#91;PSCustomObject]@{
  172.            FriendlyName = 'Business Essentials'
  173.            SkuPartNumber = 'O365_BUSINESS_ESSENTIALS'
  174.            DisabledPlanNames = @()
  175.        }
  176.    )
  177.  
  178.    $LicenseObject = $LicenseObjectArray | ? { $_.FriendlyName -eq $License }
  179.  
  180.    if(-not $LicenseObject) {
  181.        Write-Output 'License is not supported'
  182.        return
  183.    }
  184.  
  185.    $sku = Get-MgSubscribedSku -All -ErrorAction Stop | Where { $_.SkuPartNumber -eq $LicenseObject.SkuPartNumber }
  186.  
  187.    $disabledPlans = $sku.ServicePlans |  Where { $_.ServicePlanName -in $LicenseObject.DisabledPlanNames } | Select -ExpandProperty ServicePlanId
  188.  
  189.    if(-not $disabledPlans) { $disabledPlans = @()}
  190.    
  191.    $addLicenses = @(
  192.        @{
  193.            SkuId = $sku.SkuId
  194.            DisabledPlans = $disabledPlans
  195.        }
  196.    )
  197.  
  198.    Set-MgUserLicense -UserId $UserPrincipalName -AddLicenses $addLicenses -RemoveLicenses @() -ErrorAction Stop | Out-Null
  199.  
  200.    Write-Output "Successfully assigned the license $License to the user $UserPrincipalName"
  201. } catch {
  202.    Write-Output "Error while executing the script"
  203.    Write-Error $_
  204. </code></pre>
  205. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/assigning-licenses/">Assigning Licenses</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  206. ]]></content:encoded>
  207. </item>
  208. <item>
  209. <title>How to run a PowerShell (PS1) script</title>
  210. <link>http://www.servervitalsigns.com/how-to-run-a-powershell-ps1-script/</link>
  211. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  212. <pubDate>Thu, 02 Feb 2023 22:20:14 +0000</pubDate>
  213. <category><![CDATA[PowerScripts]]></category>
  214. <category><![CDATA[PowerShell]]></category>
  215. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1281</guid>
  216.  
  217. <description><![CDATA[<p><img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2021/12/powershell-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />PowerShell scripts are saved with a .ps1 file extension and can be executed in the PowerShell environment. Running a PowerShell script is a simple process and can be done in a few different ways. The first method is to run the script by entering the full path to the script file in the PowerShell window: [&#8230;]</p>
  218. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/how-to-run-a-powershell-ps1-script/">How to run a PowerShell (PS1) script</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  219. ]]></description>
  220. <content:encoded><![CDATA[<img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2021/12/powershell-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />
  221. <p>PowerShell scripts are saved with a .ps1 file extension and can be executed in the PowerShell environment. Running a PowerShell script is a simple process and can be done in a few different ways.</p>
  222.  
  223.  
  224.  
  225. <p>The first method is to run the script by entering the full path to the script file in the PowerShell window:</p>
  226.  
  227.  
  228.  
  229. <pre class="wp-block-code"><code>.\path\to\your\script.ps1</code></pre>
  230.  
  231.  
  232.  
  233. <p>Replace “path\to\your\script.ps1” with the actual path to the script you want to run.</p>
  234.  
  235.  
  236.  
  237. <p>Another way to run a PowerShell script is by using the <code>Invoke-Expression</code> cmdlet. This cmdlet allows you to run a string as a PowerShell expression:</p>
  238.  
  239.  
  240.  
  241. <pre class="wp-block-code"><code>Invoke-Expression -Command ".\path\to\your\script.ps1"</code></pre>
  242.  
  243.  
  244.  
  245. <p>Finally, you can also run a PowerShell script by double-clicking on the script file in Windows Explorer. This will launch the PowerShell environment and run the script.</p>
  246.  
  247.  
  248.  
  249. <p>In conclusion, running a PowerShell script is a straightforward process. By using one of the methods outlined above, you can easily run scripts in the PowerShell environment and automate tasks.</p>
  250.  
  251.  
  252.  
  253. <p>Of course, there is a better way to run PowerShell if you want to safely delegate your scripts to others, and that’s using <a href="http://home">PowerScripts</a>.</p>
  254. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/how-to-run-a-powershell-ps1-script/">How to run a PowerShell (PS1) script</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  255. ]]></content:encoded>
  256. </item>
  257. <item>
  258. <title></title>
  259. <link>http://www.servervitalsigns.com/1278-2/</link>
  260. <comments>http://www.servervitalsigns.com/1278-2/#respond</comments>
  261. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  262. <pubDate>Thu, 02 Feb 2023 22:07:27 +0000</pubDate>
  263. <category><![CDATA[Uncategorized]]></category>
  264. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1278</guid>
  265.  
  266. <description><![CDATA[<p>PowerShell scripts are saved with a .ps1 file extension and can be executed in the PowerShell environment. Running a PowerShell script is a simple process and can be done in a few different ways. The first method is to run the script by entering the full path to the script file in the PowerShell window: [&#8230;]</p>
  267. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/1278-2/"></a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  268. ]]></description>
  269. <content:encoded><![CDATA[
  270. <p>PowerShell scripts are saved with a .ps1 file extension and can be executed in the PowerShell environment. Running a PowerShell script is a simple process and can be done in a few different ways.</p>
  271.  
  272.  
  273.  
  274. <p>The first method is to run the script by entering the full path to the script file in the PowerShell window:</p>
  275.  
  276.  
  277.  
  278. <pre class="wp-block-code"><code>.\path\to\your\script.ps1</code></pre>
  279.  
  280.  
  281.  
  282. <p>Replace &#8220;path\to\your\script.ps1&#8221; with the actual path to the script you want to run.</p>
  283.  
  284.  
  285.  
  286. <p>Another way to run a PowerShell script is by using the <code>Invoke-Expression</code> cmdlet. This cmdlet allows you to run a string as a PowerShell expression:</p>
  287.  
  288.  
  289.  
  290. <pre class="wp-block-code"><code>Invoke-Expression -Command ".\path\to\your\script.ps1"</code></pre>
  291.  
  292.  
  293.  
  294. <p>Finally, you can also run a PowerShell script by double-clicking on the script file in Windows Explorer. This will launch the PowerShell environment and run the script.</p>
  295.  
  296.  
  297.  
  298. <p>In conclusion, running a PowerShell script is a straightforward process. By using one of the methods outlined above, you can easily run scripts in the PowerShell environment and automate tasks.</p>
  299. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/1278-2/"></a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  300. ]]></content:encoded>
  301. <wfw:commentRss>http://www.servervitalsigns.com/1278-2/feed/</wfw:commentRss>
  302. <slash:comments>0</slash:comments>
  303. </item>
  304. <item>
  305. <title>Granting a user access to a calendar</title>
  306. <link>http://www.servervitalsigns.com/granting-a-user-access-to-a-calendar/</link>
  307. <comments>http://www.servervitalsigns.com/granting-a-user-access-to-a-calendar/#respond</comments>
  308. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  309. <pubDate>Mon, 04 Apr 2022 15:33:46 +0000</pubDate>
  310. <category><![CDATA[Uncategorized]]></category>
  311. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1267</guid>
  312.  
  313. <description><![CDATA[<p><img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2021/12/powershell-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />One of the very common tasks I find myself doing as I support many of our O365 customers is granting a user access to someone else&#8217; calendar. When you do it manually, it&#8217;s a fairly boring and tedious process&#8211; 1) go to the Microsoft Exchange Admin portal and search for the user&#8217;s mailbox, 2) grant [&#8230;]</p>
  314. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/granting-a-user-access-to-a-calendar/">Granting a user access to a calendar</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  315. ]]></description>
  316. <content:encoded><![CDATA[<img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2021/12/powershell-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />
  317. <p>One of the very common tasks I find myself doing as I support many of our O365 customers is granting a user access to someone else&#8217; calendar.</p>
  318.  
  319.  
  320.  
  321. <p>When you do it manually, it&#8217;s a fairly boring and tedious process&#8211; 1) go to the Microsoft Exchange Admin portal and search for the user&#8217;s mailbox, 2) grant yourself full access, 3) go to your own mailbox and select &#8220;Open Another User&#8217;s Mailbox&#8221;.  4) Switch to their calendar view, 5) highlight their calendar and select &#8220;Sharing and Permissions&#8221;. 6) click the + button, 7) type in a user&#8217;s name to search for it, 7) select the user from the list and the appropriate permission level and click the share button.  This would take about five minutes to complete. </p>
  322.  
  323.  
  324.  
  325. <p>I got sick of doing this so I wrote a small PowerScript script to do to all that for me.  Now it takes about 30 seconds. </p>
  326.  
  327.  
  328.  
  329. <p>param(<br>[string] $SamAccountName,<br>[Parameter(HelpMessage=&#8221;User Name&#8221;)] [string] $User,<br>[string][ValidateSet(&#8216;Owner&#8217;, &#8216;Author&#8217;, &#8216;Reviewer&#8217;, &#8216;None&#8217;)] $Rights<br>)</p>
  330.  
  331.  
  332.  
  333. <p>try {</p>
  334.  
  335.  
  336.  
  337. <pre class="wp-block-code"><code>Add-MailboxFolderPermission -Identity "$($SamAccountName):\calendar"  -user $User -AccessRights $Rights
  338. Write-Output "Granted $Identity the $Rights Permission"</code></pre>
  339.  
  340.  
  341.  
  342. <p>} catch {<br>Write-Output $_.Exception.Message</p>
  343.  
  344.  
  345.  
  346. <p>}</p>
  347.  
  348.  
  349.  
  350. <p></p>
  351. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/granting-a-user-access-to-a-calendar/">Granting a user access to a calendar</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  352. ]]></content:encoded>
  353. <wfw:commentRss>http://www.servervitalsigns.com/granting-a-user-access-to-a-calendar/feed/</wfw:commentRss>
  354. <slash:comments>0</slash:comments>
  355. </item>
  356. <item>
  357. <title>An audit trail for PowerShell script execution</title>
  358. <link>http://www.servervitalsigns.com/an-audit-trail-for-powershell-script-execution/</link>
  359. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  360. <pubDate>Thu, 13 Jan 2022 18:58:53 +0000</pubDate>
  361. <category><![CDATA[PowerScripts]]></category>
  362. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1204</guid>
  363.  
  364. <description><![CDATA[<p><img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1-150x150.png" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />Native PowerShell has no audit trail. Naturally, this makes the Security Officer at banks and other security-conscious organizations (such as defense contractors) very nervous. Some companies go as far as to ban PowerShell on the desktop fully. But banning PowerShell is not the only option. PowerScripts provides a secure environment in which PowerShell scripts can [&#8230;]</p>
  365. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/an-audit-trail-for-powershell-script-execution/">An audit trail for PowerShell script execution</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  366. ]]></description>
  367. <content:encoded><![CDATA[<img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1-150x150.png" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />
  368. <p>Native PowerShell has no audit trail. Naturally, this makes the Security Officer at banks and other security-conscious organizations (such as defense contractors) very nervous. Some companies go as far as to ban PowerShell on the desktop fully. But banning PowerShell is not the only option. <a href="https://powerscripts365.com"><em>PowerScripts</em></a> provides a secure environment in which PowerShell scripts can be executed and their actions traced.</p>
  369.  
  370.  
  371.  
  372. <p>Anytime a <em>PowerScript</em> is executed an audit entry is created.&nbsp;The audit entry contains the name of the script that ran, the name of the person who ran it, when it was run, what parameters were provided, what the script output as a result, and even a copy of the script itself.</p>
  373.  
  374.  
  375.  
  376. <h2 class="wp-block-heading"><em>PowerScripts</em> makes PowerShell auditable</h2>
  377.  
  378.  
  379.  
  380. <p>The <em>PowerScripts</em> audit log contains a <strong>full transaction history</strong> of every PowerShell script which has been run in your tenant.&nbsp;&nbsp;The scripts themselves are tracked with a <strong>automatic version history</strong> so that if you look back at a specific transaction, you can see every line of code in the script which had been run at the time even if the script has since been changed.<br></p>
  381.  
  382.  
  383.  
  384. <h3 class="wp-block-heading">Search the Audit Log</h3>
  385.  
  386.  
  387.  
  388. <p>PowerScripts provides the unique ability to see exactly what was done in your environment, and by whom. What script did they run?  What was the content of the script?  What parameters were passed to the script?  What was the output of the script?  All these questions suddenly become easily answerable.</p>
  389.  
  390.  
  391.  
  392. <figure class="wp-block-image size-large"><a href="http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1.png"><img loading="lazy" decoding="async" width="1024" height="399" src="http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1-1024x399.png" alt="" class="wp-image-1205" srcset="http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1-1024x399.png 1024w, http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1-300x117.png 300w, http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1-768x299.png 768w, http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1-1536x598.png 1536w, http://www.servervitalsigns.com/wp-content/uploads/2022/01/Audit-log-2048x797-1.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /></a></figure>
  393.  
  394.  
  395.  
  396. <p>You can save this log for as long as you like, or set the log to purge automatically after a specified period.</p>
  397. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/an-audit-trail-for-powershell-script-execution/">An audit trail for PowerShell script execution</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  398. ]]></content:encoded>
  399. </item>
  400. <item>
  401. <title>How to disable MFA (multi-factor authentication) for Office365 with PowerShell</title>
  402. <link>http://www.servervitalsigns.com/how-to-disable-mfa-multi-factor-authentication-for-office365-with-powershell/</link>
  403. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  404. <pubDate>Thu, 23 Dec 2021 18:25:29 +0000</pubDate>
  405. <category><![CDATA[Office 365]]></category>
  406. <category><![CDATA[PowerScripts]]></category>
  407. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1190</guid>
  408.  
  409. <description><![CDATA[<p><img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2021/12/powershell-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />We have some customers who are so large that their employees misplace or even lose several phones a day. Our largest customer has 70,000 employees who misplace about 11 phones a day. Left in the car or on the nightstand, for example. With their phone gone, they are no longer able to use MFA so [&#8230;]</p>
  410. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/how-to-disable-mfa-multi-factor-authentication-for-office365-with-powershell/">How to disable MFA (multi-factor authentication) for Office365 with PowerShell</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  411. ]]></description>
  412. <content:encoded><![CDATA[<img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2021/12/powershell-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="" decoding="async" loading="lazy" />
  413. <p>We have some customers who are so large that their employees misplace or even lose several phones a day.  Our largest customer has 70,000 employees who misplace about 11 phones a day.  Left in the car or on the nightstand, for example.  With their phone gone, they are no longer able to use MFA so they can&#8217;t log into their accounts anymore.  For these users, MFA needs to be temporarily disabled so they can access their O365 email, Teams, etc.</p>
  414.  
  415.  
  416.  
  417. <p>This can be easily accomplished in PowerShell with a script similar to this:</p>
  418.  
  419.  
  420.  
  421. <p><span class="has-inline-color has-blue-color">$name= Read-Host -Prompt &#8220;Enter your name&#8221;<br>try {<br>$user = Get-MsolUser -UserPrincipalName $UPN -ErrorAction SilentlyContinue<br>$uName = $user.DisplayName<br>if(!$user)<br>{<br>Write-Output &#8220;No user could be found with the UPN of $UPN.&#8221;<br>}else<br>{<br>if(!($user.StrongAuthenticationRequirements))<br>{<br>Write-Output &#8220;Multi-factor authentication is already disabled for $uName($UPN)&#8221;</span><br><span class="has-inline-color has-blue-color">}<br>else<br>{<br>$EmptyArray = @()<br>Set-MsolUser -UserPrincipalName $UPN -StrongAuthenticationRequirements $EmptyArray<br>Write-Output &#8220;Multi-factor authentication was disabled for $uName($UPN)&#8221;<br>}<br>}<br>} catch {<br>Write-Output &#8220;Error:&#8221;<br>Write-Output &#8220;$_&#8221;<br>}</span></p>
  422.  
  423.  
  424.  
  425. <p>But of course, running such a script assumes you have access to the proper credentials, and that those credentials have the <a rel="noreferrer noopener" href="https://docs.microsoft.com/en-us/azure/active-directory/roles/permissions-reference" target="_blank">Authentication Administrator</a> role.  You could write a script like, but you couldn&#8217;t delegate it down to the Service Desk unless they also had such rights&#8230; and that is usually not the case.  Is there a solution?  YES!  VitalSigns now has a feature called PowerScripts.  </p>
  426.  
  427.  
  428.  
  429. <p>We think it&#8217;s such an important area of functionality that we dedicated an entire website to explaining it.  Check out our latest feature at <a href="https://powerscripts365.com/">https://powerscripts365.com/</a></p>
  430. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/how-to-disable-mfa-multi-factor-authentication-for-office365-with-powershell/">How to disable MFA (multi-factor authentication) for Office365 with PowerShell</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  431. ]]></content:encoded>
  432. </item>
  433. <item>
  434. <title>Empowering Remote Collaboration at Sherwin Williams</title>
  435. <link>http://www.servervitalsigns.com/empowering-remote-collaboration-at-sherwin-williams/</link>
  436. <comments>http://www.servervitalsigns.com/empowering-remote-collaboration-at-sherwin-williams/#respond</comments>
  437. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  438. <pubDate>Fri, 05 Mar 2021 19:53:53 +0000</pubDate>
  439. <category><![CDATA[IBM Connections]]></category>
  440. <category><![CDATA[VitalSigns]]></category>
  441. <category><![CDATA[collaboration]]></category>
  442. <category><![CDATA[HCL Connections]]></category>
  443. <category><![CDATA[HCL Domino]]></category>
  444. <category><![CDATA[HCL Domino v12]]></category>
  445. <category><![CDATA[IBM Domino]]></category>
  446. <category><![CDATA[monitoring]]></category>
  447. <category><![CDATA[Remote Work]]></category>
  448. <category><![CDATA[Remote Workforce]]></category>
  449. <category><![CDATA[reporting]]></category>
  450. <category><![CDATA[Sherwin Williams]]></category>
  451. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1163</guid>
  452.  
  453. <description><![CDATA[<p>While remote collaboration has long been a modest concern for many organizations, it wasn’t until 2020 that remote collaboration skyrocketed to the forefront. We all know about the events in 2020, which caused organizations all over the globe to rapidly modernize their workplaces to survive in this new digital arena. Many organizations were already planning [&#8230;]</p>
  454. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/empowering-remote-collaboration-at-sherwin-williams/">Empowering Remote Collaboration at Sherwin Williams</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  455. ]]></description>
  456. <content:encoded><![CDATA[
  457. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
  458. <iframe loading="lazy"  id="_ytid_31841"  width="480" height="270"  data-origwidth="480" data-origheight="270" src="https://www.youtube.com/embed/KSVwWdIWWlM?enablejsapi=1&#038;autoplay=0&#038;cc_load_policy=0&#038;cc_lang_pref=&#038;iv_load_policy=1&#038;loop=0&#038;modestbranding=0&#038;rel=1&#038;fs=1&#038;playsinline=0&#038;autohide=2&#038;theme=dark&#038;color=red&#038;controls=1&#038;" class="__youtube_prefs__  epyt-is-override  no-lazyload" title="YouTube player"  allow="fullscreen; accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen data-no-lazy="1" data-skipgform_ajax_framebjll=""></iframe>
  459. </div></figure>
  460.  
  461.  
  462.  
  463. <p> While remote collaboration has long been a modest concern for many  organizations, it wasn’t until 2020 that remote collaboration skyrocketed to the forefront. We all know about the events in 2020,  which caused organizations all over the globe to rapidly modernize their  workplaces to survive in this new digital arena. Many organizations  were already planning to gradually modernize these structures. Then  almost overnight, the pandemic turned tomorrow’s nice to haves into  yesterday’s should-haves. While each distributed workforce is unique,  they do all share the need to be connected in real-time – not only to  each other but also to all corporate resources and tools. </p>
  464.  
  465.  
  466.  
  467. <div class="wp-block-button aligncenter is-style-fill"><a class="wp-block-button__link has-white-color has-blue-background-color has-text-color has-background" href="https://rprwyatt.com/future/">On-Demand Webinar</a></div>
  468.  
  469.  
  470.  
  471. <h2 class="wp-block-heading">Embracing Change</h2>
  472.  
  473.  
  474.  
  475. <hr class="wp-block-separator has-text-color has-background has-blue-background-color has-blue-color is-style-wide"/>
  476.  
  477.  
  478.  
  479. <p> As  a long-time developer, I had numerous organizations and individuals  reach out for assistance and solutions to help navigate these turbulent  times. One organization, in particular, was Sherwin Williams, one of the  largest paint and coating manufacturers. Sherwin Williams relies  heavily on <a href="https://www.hcltechsw.com/wps/portal/products/connections">HCL Connections</a>  to keep their teams connected, engaged, and productive. For over five  years, I have worked directly with their teams and have developed  countless monitoring, reporting, and administrative features to  streamline HCL Connections management. </p>
  480.  
  481.  
  482.  
  483. <h2 class="wp-block-heading">Creating Business Value at Sherwin Williams </h2>
  484.  
  485.  
  486.  
  487. <hr class="wp-block-separator has-text-color has-background has-blue-background-color has-blue-color is-style-wide"/>
  488.  
  489.  
  490.  
  491. <p>Sherwin
  492. Williams has one of the largest deployments of HCL Connections. And
  493. they heavily rely on the collaborative solution to generate, enhance,
  494. and maintain business value. To protect their valuable investment,
  495. Sherwin Williams secured VitalSigns years ago to monitor their
  496. Connections environment – their Communities, User Activities, Adoption,
  497. etc. as well as the underlying components that affect the performance
  498. and availability of Connections.</p>
  499.  
  500.  
  501.  
  502. <p>When
  503. the pandemic hit, the drastic increase in remote workers not only
  504. caused a surge in Connections utilization but also modified how
  505. Connections was being utilized. But thankfully, with complete visibility
  506. from VitalSigns and diligent administration on their end, Sherwin
  507. Williams was prepared.</p>
  508.  
  509.  
  510.  
  511. <div class="wp-block-button aligncenter is-style-fill"><a class="wp-block-button__link has-white-color has-blue-background-color has-text-color has-background" href="https://rprwyatt.com/future/">On-Demand Webinar</a></div>
  512.  
  513.  
  514.  
  515. <h2 class="wp-block-heading"> Modern Digital Solutions </h2>
  516.  
  517.  
  518.  
  519. <hr class="wp-block-separator has-text-color has-background has-blue-background-color has-blue-color is-style-wide"/>
  520.  
  521.  
  522.  
  523. <p>Connections
  524. 7 is an exciting release full of many new features that have been able
  525. to help organizations facilitate remote collaboration within their new
  526. remote workforce. <a href="https://help.hcltechsw.com/connections/v7/admin/overview/i_ovr_r_whats_new.html">New features in Connections 7</a>
  527. like Orient Me and Touchpoint allowed Sherwin Williams to simplify
  528. daily work and easily onboard new users as the number of remote workers
  529. increased.</p>
  530.  
  531.  
  532.  
  533. <p>Thankfully,
  534. Sherwin Williams had been using VitalSigns to monitor their Connections
  535. environment for some time before the pandemic. So not only was their
  536. environment very stable, but they also had benchmark performance data,
  537. allowing them to quickly identify even the slightest defects in
  538. performance as they scaled up.</p>
  539.  
  540.  
  541.  
  542. <p>As
  543. they prepared for the influx of activity – they also leveraged
  544. VitalSigns to simulate end-user transactions and ensure their
  545. infrastructure could handle the increase. This also allowed them to
  546. quickly and proactively identify potential issues before actual end
  547. users were affected.</p>
  548.  
  549.  
  550.  
  551. <h2 class="wp-block-heading"> Building Value with Collaborative Communities </h2>
  552.  
  553.  
  554.  
  555. <hr class="wp-block-separator has-text-color has-background has-blue-background-color has-blue-color is-style-wide"/>
  556.  
  557.  
  558.  
  559. <p>As
  560. the workforce shifted – so did the style in which we communicate and
  561. collaborate. The water cooler is no longer a physical area, but could
  562. now be a Community within Connections.</p>
  563.  
  564.  
  565.  
  566. <p>Again,
  567. thankfully, Sherwin Williams was prepared. In part due to the addition
  568. of&nbsp;Community Templates&nbsp;in Connections 7, making it easy to quickly
  569. create and edit Communities. But also, because VitalSigns optimized
  570. Connections performance and availability, while also providing real-time
  571. insights into Community Activity. VitalSigns empowered Sherwin Williams
  572. to understand user behavior within their Connections Communities. With
  573. this knowledge, it became easier to analyze trends, identify&nbsp;Internal
  574. Champions,&nbsp;and make informed decisions.</p>
  575.  
  576.  
  577.  
  578. <div class="wp-block-button aligncenter is-style-fill"><a class="wp-block-button__link has-white-color has-blue-background-color has-text-color has-background" href="https://rprwyatt.com/future/">On-Demand Webinar</a></div>
  579.  
  580.  
  581.  
  582. <h2 class="wp-block-heading"> Empowering the Workforce with Culture &amp; Leadership </h2>
  583.  
  584.  
  585.  
  586. <hr class="wp-block-separator has-text-color has-background has-blue-background-color has-blue-color is-style-wide"/>
  587.  
  588.  
  589.  
  590. <p>The
  591. Internal Champions report in VitalSigns identifies subject matter
  592. experts within Connections, across all Communities, Departments, and
  593. teams. Organizations can then promote their Internal Champions as a
  594. valuable resource for users seeking assistance on a specific topic.</p>
  595.  
  596.  
  597.  
  598. <p>It
  599. was a great benefit to know who your Internal Champions were before the
  600. workplace disruption in early 2020. This allowed organizations to
  601. drastically increase their remote user experience by promoting their
  602. Internal Champions, and by positioning them in places where they could
  603. make the biggest impact.</p>
  604.  
  605.  
  606.  
  607. <p>It
  608. was beneficial to knowing who the Internal Champions were before the
  609. shift. But it was even more so to actively track Champion activity
  610. throughout, and following the shift. We began to see a new kind of
  611. “Champion” emerge. One whose role goes beyond a subject matter expert,
  612. and is also prepared to take ownership and empower their coworkers to
  613. overcome geological barriers.</p>
  614.  
  615.  
  616.  
  617. <p>Like
  618. they say you are only as strong as your weakest link – we quickly
  619. learned that it was just as important to identify those who were
  620. struggling to adopt the solution. Now I didn’t want to create a tattle
  621. tale tool, quite the opposite. I wanted to provide managers, team leads,
  622. and even Internal Champions with a way to quickly address user pain
  623. points and to provide training or assistance where it is needed.</p>
  624.  
  625.  
  626.  
  627. <p>VitalSigns
  628. was able to provide with more than just which individuals were
  629. struggling, giving them insights into why individuals were struggling.
  630. By understanding the why, team leaders and managers can encourage,
  631. educate, and properly empower every employee. In the end, Connections
  632. provided them with the collaborative platform to stay connected – and
  633. VitalSigns gave them the insights and stability to maximize their
  634. collaborative potential.</p>
  635.  
  636.  
  637.  
  638. <h2 class="wp-block-heading"> Why RPR Wyatt? </h2>
  639.  
  640.  
  641.  
  642. <hr class="wp-block-separator has-text-color has-background has-blue-background-color has-blue-color is-style-wide"/>
  643.  
  644.  
  645.  
  646. <p>RPR
  647. Wyatt’s team of experts has been helping organizations on the Domino
  648. platform for the last two decades and we plan to continue assisting
  649. Domino organizations for decades to come.</p>
  650.  
  651.  
  652.  
  653. <p>&nbsp;From
  654. enterprise organizations to family businesses, RPR Wyatt is the go-to
  655. provider for monitoring, administration, development, licensing, and
  656. reporting for all things HCL Domino.</p>
  657.  
  658.  
  659.  
  660. <p>&nbsp;RPR Wyatt has partnered with HCL Software to help organizations empower  their workforce and drive future business value using modern digital  solutions and expert digital services.</p>
  661.  
  662.  
  663.  
  664. <hr class="wp-block-separator has-text-color has-background has-blue-background-color has-blue-color is-style-wide"/>
  665.  
  666.  
  667.  
  668. <h3 class="has-text-align-center wp-block-heading"><strong>Take advantage of our exclusive offerings:</strong></h3>
  669.  
  670.  
  671.  
  672. <div class="wp-block-columns is-layout-flex wp-container-core-columns-layout-1 wp-block-columns-is-layout-flex">
  673. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow">
  674. <h5 class="has-text-align-center wp-block-heading">Free Monitoring</h5>
  675.  
  676.  
  677.  
  678. <div class="wp-block-image"><figure class="aligncenter size-large"><a href="http://www.servervitalsigns.com/wp-content/uploads/2021/03/health.png"><img loading="lazy" decoding="async" width="128" height="128" src="http://www.servervitalsigns.com/wp-content/uploads/2021/03/health.png" alt="Remote Collaboration" class="wp-image-1172"/></a></figure></div>
  679.  
  680.  
  681.  
  682. <p class="has-text-align-center">Try VitalSigns monitoring and reporting for everything Domino, risk-free for six months.<br> </p>
  683.  
  684.  
  685.  
  686. <div class="wp-block-button aligncenter is-style-fill"><a class="wp-block-button__link has-white-color has-blue-background-color has-text-color has-background" href="mailto:info@rprwyatt.com?subject=I would like to try VitalSigns for free ">Get Started</a></div>
  687. </div>
  688.  
  689.  
  690.  
  691. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow">
  692. <h5 class="has-text-align-center wp-block-heading">Free Services</h5>
  693.  
  694.  
  695.  
  696. <div class="wp-block-image"><figure class="aligncenter size-large"><a href="http://www.servervitalsigns.com/wp-content/uploads/2021/03/tools.png"><img loading="lazy" decoding="async" width="128" height="128" src="http://www.servervitalsigns.com/wp-content/uploads/2021/03/tools.png" alt="Remote Collaboration" class="wp-image-1173"/></a></figure></div>
  697.  
  698.  
  699.  
  700. <p class="has-text-align-center"> Rapidly modernize deployment, migrations and upgrades with access to free professional service hours. </p>
  701.  
  702.  
  703.  
  704. <div class="wp-block-button aligncenter"><a class="wp-block-button__link has-white-color has-blue-background-color has-text-color has-background" href="mailto:info@rprwyatt.com?subject=I am interested in free services">Get Started</a></div>
  705. </div>
  706.  
  707.  
  708.  
  709. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow">
  710. <h5 class="has-text-align-center wp-block-heading">Free Development</h5>
  711.  
  712.  
  713.  
  714. <div class="wp-block-image"><figure class="aligncenter size-large"><a href="http://www.servervitalsigns.com/wp-content/uploads/2021/03/development.png"><img loading="lazy" decoding="async" width="128" height="128" src="http://www.servervitalsigns.com/wp-content/uploads/2021/03/development.png" alt="Remote Collaboration" class="wp-image-1174"/></a></figure></div>
  715.  
  716.  
  717.  
  718. <p class="has-text-align-center"> Expand and enhance development capabilities with free access to the <a href="https://secureservercdn.net/192.169.223.13/126.0b0.myftpupload.com/wp-content/uploads/2021/02/Domino-Volt-Quick-Start.pdf">Domino Volt Quick Start Program</a>. </p>
  719.  
  720.  
  721.  
  722. <div class="wp-block-button aligncenter"><a class="wp-block-button__link has-white-color has-blue-background-color has-text-color has-background" href="mailto:info@rprwyatt.com?subject=I am interested in the Domino Volt Quick Start Program">Get Started</a></div>
  723. </div>
  724. </div>
  725.  
  726.  
  727.  
  728. <h1 class="has-text-align-center wp-block-heading">Contact Us</h1>
  729.  
  730.  
  731.  
  732. <hr class="wp-block-separator has-text-color has-background has-blue-background-color has-blue-color is-style-wide"/>
  733.  
  734.  
  735.  
  736. <div class="wp-block-columns is-layout-flex wp-container-core-columns-layout-2 wp-block-columns-is-layout-flex">
  737. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow">
  738. <figure class="wp-block-image size-large"><a href="http://www.servervitalsigns.com/wp-content/uploads/2021/03/RPR-Wyatt-logo-no-back.png"><img loading="lazy" decoding="async" width="1024" height="486" src="http://www.servervitalsigns.com/wp-content/uploads/2021/03/RPR-Wyatt-logo-no-back-1024x486.png" alt="" class="wp-image-1176" srcset="http://www.servervitalsigns.com/wp-content/uploads/2021/03/RPR-Wyatt-logo-no-back-1024x486.png 1024w, http://www.servervitalsigns.com/wp-content/uploads/2021/03/RPR-Wyatt-logo-no-back-300x142.png 300w, http://www.servervitalsigns.com/wp-content/uploads/2021/03/RPR-Wyatt-logo-no-back-768x365.png 768w, http://www.servervitalsigns.com/wp-content/uploads/2021/03/RPR-Wyatt-logo-no-back-1536x729.png 1536w, http://www.servervitalsigns.com/wp-content/uploads/2021/03/RPR-Wyatt-logo-no-back-624x296.png 624w, http://www.servervitalsigns.com/wp-content/uploads/2021/03/RPR-Wyatt-logo-no-back.png 2035w" sizes="(max-width: 1024px) 100vw, 1024px" /></a></figure>
  739. </div>
  740.  
  741.  
  742.  
  743. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow">
  744. <h5 class="has-text-align-center wp-block-heading"><a href="mailto:info@rprwyatt.com">info@rprwyatt.com</a></h5>
  745.  
  746.  
  747.  
  748. <h5 class="has-text-align-center wp-block-heading"><a href="http://www.rprwyatt.com" data-type="URL" data-id="www.rprwyatt.com">www.rprwyatt.com</a></h5>
  749.  
  750.  
  751.  
  752. <h5 class="has-text-align-center wp-block-heading">602-263-7779</h5>
  753. </div>
  754. </div>
  755.  
  756.  
  757.  
  758. <div class="wp-block-columns is-layout-flex wp-container-core-columns-layout-3 wp-block-columns-is-layout-flex">
  759. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"></div>
  760.  
  761.  
  762.  
  763. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow">
  764. <p class="has-white-color has-text-color">remote collaboration</p>
  765. </div>
  766.  
  767.  
  768.  
  769. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"></div>
  770. </div>
  771. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/empowering-remote-collaboration-at-sherwin-williams/">Empowering Remote Collaboration at Sherwin Williams</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  772. ]]></content:encoded>
  773. <wfw:commentRss>http://www.servervitalsigns.com/empowering-remote-collaboration-at-sherwin-williams/feed/</wfw:commentRss>
  774. <slash:comments>0</slash:comments>
  775. </item>
  776. <item>
  777. <title>Proactive Office 365 Administration: Scheduled PowerShell scripts</title>
  778. <link>http://www.servervitalsigns.com/proactive-o365-administration-scheduled-powershell-scripts/</link>
  779. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  780. <pubDate>Thu, 04 Jun 2020 19:36:13 +0000</pubDate>
  781. <category><![CDATA[Office 365]]></category>
  782. <category><![CDATA[PowerScripts]]></category>
  783. <category><![CDATA[VitalSigns]]></category>
  784. <category><![CDATA[Administration]]></category>
  785. <category><![CDATA[email]]></category>
  786. <category><![CDATA[Microosft Office 365]]></category>
  787. <category><![CDATA[microsoft]]></category>
  788. <category><![CDATA[Microsoft Exchange]]></category>
  789. <category><![CDATA[Microsoft Teams]]></category>
  790. <category><![CDATA[o365]]></category>
  791. <category><![CDATA[PowerShell]]></category>
  792. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1152</guid>
  793.  
  794. <description><![CDATA[<p>The power of scheduled PowerScripts PowerScripts is a feature within VitalSigns that allows for the controlled execution of Microsoft PowerShell scripts and commands. Starting with VitalSigns version 6.2 you can now schedule PowerScripts to run on a daily, weekly, or monthly basis. This opens the door for a variety of proactive measures you can take [&#8230;]</p>
  795. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/proactive-o365-administration-scheduled-powershell-scripts/">Proactive Office 365 Administration: Scheduled PowerShell scripts</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  796. ]]></description>
  797. <content:encoded><![CDATA[
  798. <h2 class="wp-block-heading">The power of scheduled PowerScripts</h2>
  799.  
  800.  
  801.  
  802. <p>PowerScripts is a feature within VitalSigns that allows for the controlled execution of Microsoft PowerShell scripts and commands.  Starting with VitalSigns version 6.2 you can now schedule PowerScripts to run on a daily, weekly, or monthly basis.</p>
  803.  
  804.  
  805.  
  806. <p>This opens the door for a variety of proactive measures you can take automatically to keep your Office 365/Microsoft 365 environment running securely and efficiently.</p>
  807.  
  808.  
  809.  
  810. <h2 class="wp-block-heading">Identify compromised mail files</h2>
  811.  
  812.  
  813.  
  814. <p>You might be wondering what kind of script you might want to run on a daily basis.  Consider the case of a user&#8217;s mail account getting compromised by a hacker. Would the user even know?  Perhaps not, at least not right away.  But that&#8217;s where scheduled PowerScripts come in.  If a hacker gets into a user&#8217;s mail it&#8217;s normally for one of two reasons: 1) to steal information or 2) to send out SPAM.  To cover their tracks hackers normally create mail rules which can be identified.  You cannot expect users to periodically look at their own mail rules to see if there is one which they did not create.  When was the last time you looked at your mail rules?</p>
  815.  
  816.  
  817.  
  818. <h4 class="wp-block-heading">Stealing Information</h4>
  819.  
  820.  
  821.  
  822. <p>When a hacker wants to steal corporate information, a great way to do that is to penetrate a user&#8217;s mail and create a mail rule which automatically forwards all incoming mail to an external email address.</p>
  823.  
  824.  
  825.  
  826. <h4 class="wp-block-heading">Sending out SPAM</h4>
  827.  
  828.  
  829.  
  830. <p>When a hacker wants to send out SPAM from a user&#8217;s mail account they will worry that some of the messages they send will be to bad, and the message might bounce back as undeliverable.  If this happens the user will see the message and think &#8220;hey, I didn&#8217;t send that!&#8221;  But the hacker doesn&#8217;t want this to happen so they will create a rule to delete inbound mail. </p>
  831.  
  832.  
  833.  
  834. <h4 class="wp-block-heading">Solution</h4>
  835.  
  836.  
  837.  
  838. <p>VitalSigns comes with pre-written scripts which will identify potentially troubling mail rules and it even includes scripts which allow the service desk to disable these rules.   We don&#8217;t disable the rules automatically because there may be valid business reasons to have such rules but &#8211; of course &#8211; you can modify the included scripts in any way you desire to fully meet your needs. </p>
  839.  
  840.  
  841.  
  842. <p>We think this is a powerful and proactive way to keep a watchful eye on the security of your end user mail accounts automatically and regularly.   This concept can be extended in an  infinite variety and we welcome your suggestions for additional scripts we can include in the product. </p>
  843.  
  844.  
  845.  
  846. <p></p>
  847.  
  848.  
  849.  
  850. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="499" src="http://www.servervitalsigns.com/wp-content/uploads/2020/06/Screen-Shot-2020-06-04-at-5.18.27-PM-1024x499.png" alt="" class="wp-image-1156" srcset="http://www.servervitalsigns.com/wp-content/uploads/2020/06/Screen-Shot-2020-06-04-at-5.18.27-PM-1024x499.png 1024w, http://www.servervitalsigns.com/wp-content/uploads/2020/06/Screen-Shot-2020-06-04-at-5.18.27-PM-300x146.png 300w, http://www.servervitalsigns.com/wp-content/uploads/2020/06/Screen-Shot-2020-06-04-at-5.18.27-PM-768x374.png 768w, http://www.servervitalsigns.com/wp-content/uploads/2020/06/Screen-Shot-2020-06-04-at-5.18.27-PM-1536x749.png 1536w, http://www.servervitalsigns.com/wp-content/uploads/2020/06/Screen-Shot-2020-06-04-at-5.18.27-PM-2048x998.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
  851.  
  852.  
  853.  
  854. <h2 class="wp-block-heading">What are PowerScripts?</h2>
  855.  
  856.  
  857.  
  858. <p>PowerScripts is a feature within VitalSigns that allows for the controlled execution of Microsoft PowerShell scripts and commands. PowerScripts provide a secure wrapper around PowerShell scripts that run against of a specific thing (a Team a User, a Mailbox, a folder, etc.) or against selected things (a group of mailboxes, for example). PowerScripts are executed using stored credentials&#8211; which the user cannot see&#8211; and create an audit trail so you will know who did what, when and to what.  PowerScripts can also be scheduled to run on a recurrent basis to proactively identify or prevent problems. </p>
  859. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/proactive-o365-administration-scheduled-powershell-scripts/">Proactive Office 365 Administration: Scheduled PowerShell scripts</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  860. ]]></content:encoded>
  861. </item>
  862. <item>
  863. <title>Support Managers: Harness the Power(Shell) within Office 365</title>
  864. <link>http://www.servervitalsigns.com/support-managers-harness-the-powershell-within-office-365/</link>
  865. <comments>http://www.servervitalsigns.com/support-managers-harness-the-powershell-within-office-365/#respond</comments>
  866. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  867. <pubDate>Fri, 24 Apr 2020 17:42:33 +0000</pubDate>
  868. <category><![CDATA[Office 365]]></category>
  869. <category><![CDATA[PowerScripts]]></category>
  870. <category><![CDATA[Teams]]></category>
  871. <category><![CDATA[VitalSigns]]></category>
  872. <category><![CDATA[Azure]]></category>
  873. <category><![CDATA[exchange]]></category>
  874. <category><![CDATA[Help Desk]]></category>
  875. <category><![CDATA[microsoft]]></category>
  876. <category><![CDATA[office 365]]></category>
  877. <category><![CDATA[PowerShell]]></category>
  878. <category><![CDATA[Service Desk]]></category>
  879. <category><![CDATA[SharePoint]]></category>
  880. <category><![CDATA[Support Desk]]></category>
  881. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1141</guid>
  882.  
  883. <description><![CDATA[<p>In light of recent events, we have seen a massive influx of remote workers, resulting in a substantial increase in Support Desk tickets. Support Desk staff have been bombarded with various tickets, making it difficult to keep up with their typical daily tasks. Some say the obvious solution is to add more staff members to [&#8230;]</p>
  884. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/support-managers-harness-the-powershell-within-office-365/">Support Managers: Harness the Power(Shell) within Office 365</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  885. ]]></description>
  886. <content:encoded><![CDATA[<p>In light of recent events, we have seen a massive influx of remote workers, resulting in a substantial increase in Support Desk tickets. Support Desk staff have been bombarded with various tickets, making it difficult to keep up with their typical daily tasks. Some say the obvious solution is to add more staff members to reduce the workload of the existing staff. However, when you factor in the cost to hire – recruitment, training, salaries, etc. – you quickly realize adding more people is not the most efficient solution.</p>
  887. <p>We say, <strong>equip your Support Desk with PowerScripts so each employee can accomplish more,</strong> rather than less. PowerScripts allows each employee to accomplish more – almost immediately. PowerScripts allows any authorized user to harness the capabilities of PowerShell to identify, mitigate, address, and even prevent issues in Office 365.</p>
  888. <p><strong><a href="https://zoom.us/webinar/register/7115874955338/WN_M9MIBs2aQN6miRl8d2vcRw">Join our 15 minute Express Webinar</a> </strong>on <strong>Tuesday, April 28<sup>th</sup> at 12 pm EDT / 9 am PDT</strong> to see how you can use PowerScripts to:</p>
  889. <p>• Configure and enable remote workers<br>• Identify and remediate compromised mailboxes<br>• Fulfill Support Requests quickly and effectively</p>
  890. <p style="text-align: center;"><a role="button" href="https://zoom.us/webinar/register/7115874955338/WN_M9MIBs2aQN6miRl8d2vcRw"><br>REGISTER NOW!<br></a></p>
  891. <p></p>
  892. <p></p><center><strong>Take advantage of this Webinar BOGO</strong> – buy a year subscription and get an additional year free!</center><p></p>
  893. <p style="text-align: center;">Want more? Check out our other recent Express Webinars by clicking the banner below:</p>
  894. <p><a href="www.rprwyatt.com/resource"><img loading="lazy" decoding="async" class="aligncenter" src="http://www.servervitalsigns.com/wp-content/uploads/2020/04/service-desk-banner-100.jpg" sizes="(max-width: 675px) 100vw, 675px" srcset="http://www.servervitalsigns.com/wp-content/uploads/2020/04/service-desk-banner-100.jpg 675w, http://www.servervitalsigns.com/wp-content/uploads/2020/04/service-desk-banner-100-300x132.jpg 300w" alt="Support Manager" width="675" height="296"></a></p>
  895.  
  896.  
  897. <h2 class="wp-block-heading">What are PowerScripts?</h2>
  898.  
  899.  
  900.  
  901. <p>PowerScripts is a feature within VitalSigns that allows for the controlled execution of Microsoft PowerShell scripts and commands. PowerScripts provide a secure wrapper around PowerShell scripts that run against of a specific thing (a Team a User, a Mailbox, a folder, etc.) or against selected things (a group of mailboxes, for example). PowerScripts are executed using stored credentials&#8211; which the user cannot see&#8211; and create an audit trail so you will know who did what, when and to what.  PowerScripts can also be scheduled to run on a recurrent basis to proactively identify or prevent problems. </p>
  902. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/support-managers-harness-the-powershell-within-office-365/">Support Managers: Harness the Power(Shell) within Office 365</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  903. ]]></content:encoded>
  904. <wfw:commentRss>http://www.servervitalsigns.com/support-managers-harness-the-powershell-within-office-365/feed/</wfw:commentRss>
  905. <slash:comments>0</slash:comments>
  906. </item>
  907. <item>
  908. <title>Taming Teams: Handling the Sudden Surge of Admin Requests</title>
  909. <link>http://www.servervitalsigns.com/taming-teams-handling-the-sudden-surge-of-admin-requests/</link>
  910. <comments>http://www.servervitalsigns.com/taming-teams-handling-the-sudden-surge-of-admin-requests/#respond</comments>
  911. <dc:creator><![CDATA[VitalSigns]]></dc:creator>
  912. <pubDate>Fri, 03 Apr 2020 17:53:23 +0000</pubDate>
  913. <category><![CDATA[Teams]]></category>
  914. <category><![CDATA[Administration]]></category>
  915. <category><![CDATA[COVID-19]]></category>
  916. <category><![CDATA[Microsoft Office 365]]></category>
  917. <category><![CDATA[Microsoft Teams]]></category>
  918. <category><![CDATA[o365]]></category>
  919. <category><![CDATA[PowerShell]]></category>
  920. <category><![CDATA[Service Desk]]></category>
  921. <guid isPermaLink="false">http://www.servervitalsigns.com/?p=1132</guid>
  922.  
  923. <description><![CDATA[<p><img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2020/04/Stressed-Out-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="Teams Admin" decoding="async" loading="lazy" />Adoption of Microsoft Teams was gaining traction before COVID-19 but has now quickly shifted from an elective to a necessity. With Teams usage growing as much as 1,000%, we are also seeing the number of admin requests increasing just as drastically. Administrators are now seeking force-multiplying tools, like PowerShell, to empower the front-line to handle [&#8230;]</p>
  924. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/taming-teams-handling-the-sudden-surge-of-admin-requests/">Taming Teams: Handling the Sudden Surge of Admin Requests</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  925. ]]></description>
  926. <content:encoded><![CDATA[<img width="150" height="150" src="http://www.servervitalsigns.com/wp-content/uploads/2020/04/Stressed-Out-150x150.jpg" class="attachment-thumbnail size-thumbnail wp-post-image" alt="Teams Admin" decoding="async" loading="lazy" />
  927. <p>Adoption of Microsoft Teams was gaining traction before COVID-19 but has now quickly shifted from an elective to a necessity. With Teams usage growing as much as 1,000%, we are also seeing the number of admin requests increasing just as drastically. Administrators are now seeking force-multiplying tools, like PowerShell, to empower the front-line to handle this increase in demand. Unfortunately, only very few organizations have a team of PowerShell experts on hand.</p>
  928.  
  929.  
  930.  
  931. <p><strong>Watch our brief recording to learn how to:</strong></p>
  932.  
  933.  
  934.  
  935. <p>• Streamline and schedule daily tasks to free up resources<br>• Securely delegate PowerShell scripting to users with no prior experience<br>• Maintain in complete control with Role-based Delegation and Audit Trails</p>
  936.  
  937.  
  938.  
  939. <p></p>
  940.  
  941.  
  942.  
  943. <p><strong>Watch now:</strong><a href="https://bit.ly/tamingteams"> https://bit.ly/tamingteams</a></p>
  944.  
  945.  
  946.  
  947. <div class="wp-block-image"><figure class="aligncenter"><a href="https://rprwyatt.com/pswebinar"><img decoding="async" src="https://rprwyatt.com/wp-content/uploads/2020/04/ps-ban.png" alt="" class="wp-image-5678"/></a></figure></div>
  948. <p>The post <a rel="nofollow" href="http://www.servervitalsigns.com/taming-teams-handling-the-sudden-surge-of-admin-requests/">Taming Teams: Handling the Sudden Surge of Admin Requests</a> appeared first on <a rel="nofollow" href="http://www.servervitalsigns.com">VitalSigns and PowerScripts Blog</a>.</p>
  949. ]]></content:encoded>
  950. <wfw:commentRss>http://www.servervitalsigns.com/taming-teams-handling-the-sudden-surge-of-admin-requests/feed/</wfw:commentRss>
  951. <slash:comments>0</slash:comments>
  952. </item>
  953. </channel>
  954. </rss>
  955.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.servervitalsigns.com/feed/

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda