What Version of Windows PowerShell do I have running?

How to determine what version of Windows PowerShell is installed on your windows server?

Solution

Open PowerShell and run

$PSVersionTable.PSVersion

You will then see the result displayed obviously.

Windows PowerShell Module you receive NotSpecified: (:) [Import-Module], FileLoadException

This is a typical error for Modules that have been downloaded from the internet and are not given permission to run on the computer.

The solution

Really Easy. 

Open PowerShell

Navigate to the directory in the error message that contains the Module you intend to run. Running a command like:

cd C:\Users\administrator\Documents\WindowsPowerShell\Modules\ACMESharp\

Then Run the Command: 

Get-ChildItem . | Unblock-File

This will set the module files to be able to be used by PowerShell

That’s it. Now the module should run fine.

Update 9.2.02

Improved

– We have found and improved some of the Decode Weather code that struggled with certain specific locations that publish non standard METAR and TAF data.

Added

– New pattern recognition code that better handles non standard WX information for decode.

– Added Variable Winds Decode.

– Variable Visibility Decode.

– Recent SX WX Decode

– Sea Status in WX Decode

Notes

As it turns out, the decoding of weather world wide is rather complex. It is surprising just how many countries have their own format and data sets. Russia with Runway snow and braking information, temperate in different units, QNH, auto machine forecasts to name a few. We hop that any inaccuracies are reported via the feedback within the app, and screen shots.

Update 9.2.01

Improved

– Improved the retrieval of Weather TAF and TTF in multi thread and multi station simultaneous download.

Added

– This release includes decode information for TTF METAR and TAF data on a worldwide scale.

Notes

As it turns out, the decoding of weather world wide is rather complex. It is surprising just how many countries have their own format and data sets. Russia with Runway snow and braking information, temperate in different units, QNH, auto machine forecasts to name a few. We hop that any inaccuracies are reported via the feedback within the app, and screen shots.

Team Foundation Server 2017 HTTP code 413: Request Entity Too Large

While working with a new out of the box TFS 2017, the following error was given when uploading files that were 11 MEG. Not particularly big, but hay this is Microsoft. I say this having wasted a lot of time trying to get the RTM version of TFS 2017 to work, only to find out that web site login is broken out of the box, and SP1 fixed my issues. (Back to the Balmer days!).

Anyway the configuration we are using that would appear to make a difference here is that we took on the Microsoft suggestion at setup to use HTPS and SSL. So using the self signing certificates forcing the SSL connection, we find that the out of the box setup for Team Foundation Server 2017 with SP1 installed has this error on large file upload.

The FiX

• Open IISNavigate under Team Foundation Web Site
• Scroll down to Management and open Configuration EditorSelect following section (drop down at the top) system.webServer and expand it,
• then locate serverRuntimeyou’ll
• find there the current value of uploadReadAheadSize value, which you can change. We found that the default value was 49512 – We changed it to: 89152 
• 
• Apply your changes in the top right
   
• Then in a command prompts – Ran “iisreset”
• Problem fixed

Problem

While trying to run the OAuth provider setup in Microsoft Dynamics CRM, to configure among other things the Post-instillation setup to allow connectivity by devices and applications. I was banging my head on a problem following the instructions:

Driving me nuts!

The Fix

Turns out from these instructions found here: https://msdn.microsoft.com/en-us/library/dn531010.aspx

That an additional step is required:

Add-PSSnapin Microsoft.Crm.PowerShell

Cannot Login to a Previously working Microsoft CRM IFD

A previously working IFD deployment of CRM 2016 (but could be CRM 2015 or CRM 2013). About 1 year after you set the system up, you start receiving: An error has occurred. 
Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization’s Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support.

When researching this error, we suspected what it was, and related to an article we covered here: http://www.interactivewebs.com/blog/index.php/crm-2013/microsoft-crm-2013-or-2015-event-id-1309-adfs-ifd-resolution/

However we never found and EVENT ID 1309 or anything close to that in our logs. The closest error we found (and we are not even certain that it was pointing as a result fo this problem) was the error:  EVENT ID 415

The SSL certificate does not contain all UPN suffix values that exist in the enterprise.  Users with UPN suffix values not represented in the certificate will not be able to Workplace-Join their devices.  For more information, see http://go.microsoft.com/fwlink/?LinkId=311954.

The Problem

This problem arises from a Certificate Rollover that the ADFS server does about 1 month out from your 1 year anniversary. The problem is that the ADFS certificate rolls over, but the CRM configuration does not pickup that new certificate.

The Fix

o locate your ADFS Certificates, navigate to the ADFS Console. Under “Service”, click on “Certificates”, where you will find a Primary and Secondary certificate. If the current date is close to the date of your Primary certificate “Effective Date”, it’s safe to assume that this is the underlying issue.

To resolve this issue:

1. Navigate to the ADFS Console >> Trust Relationships >> Relying Party Trusts.
2. Right click on the trust and select “Update from Federation Metadata…”
a. If there are two trusts, do them both. This may be a case where you have one for Internal and External.

3. Open Command Prompt. Be sure to right-click and “Run as Administrator”.
a. From within CMD, type “iisreset”.

4. Open “Services” and restart the “ADFS” service.

a. If ADFS does not start, be sure to check the “Windows Internal Database” service and make sure it is started, and then try restarting the ADFS service.

If these initial steps do not resolve your issue for any reason, continue with the following steps below:

5. Navigate to “CRM Deployment Manager”.
a. Run “Configure Claims-Based Authentication” wizard, upper right hand corner.
b. Click “Next” all the way through the wizard, nothing needs to be changed here.

6. Run “Configure Internet Facing Deployment” wizard.
a. Click “Next” all the way through the wizard, nothing needs to be changed here either.

7. Now, perform Steps 1-4 again as outlined above.
a. Update Federation Metadata
b. IISReset
c. Restart ADFS Service

Your users should be able to log-in to Dynamics CRM again. I hope you find this helpful and that it resolved your issue.

Outlook Mac Office 365 Sorry, we’re having server problems, so we can’t add Office 365 SharePoint right now. Please try again later”

For no particular reason you end up with an error message: Outlook Mac Office 365 Sorry, we’re having server problems, so we can’t add Office 365 SharePoint right now. Please try again later”

This starts to ask you for two or three factor authentication on your email accounts that are based on Office 365 product. My issues started December 2016

To Resolve this error:

1. Make sure you have quitted Outlook and other Office apps. Go to KeyChain Access 

2. Search “Exchange” under Login –> All Items and delete everything 
3. Search “Office” and delete everything 
4. Search “ADAL” and delete everything  
5. Launch Outlook 
6. You will get the activation prompt.  If the account is already added, you will see the password prompt for app and ADAL again. Please do 2-Factor Authentication if asked. And then you should be able to login.

Cannot be sure what changed at Microsoft end to cause this, but obviously it is related to certificates.