If you are getting a message for your recently developed .Net application when you publish to the server to the effect of:
Chances are the server you are deploying to does not have the appropriate framework to support your app.
Download the Microsoft .Net Framework 4.6.1 and install it to resolve this. It will likely require a server reboot to complete it so don’t do it on prod mid-day! Hope this helps, questions are welcome!
Need to deliver or better understand the AD groups associated with your SharePoint site collection? Try this:
$SPWebApp = Get-SPWebApplication http://sitecollectionURLhere/
foreach ($SPSite in $SPWebApp.Sites)
{
write-host -foregroundcolor green "Working on Site Collection: " + $SPsite.RootWeb.Title
$SiteURL = $SPsite.RootWeb.URL
$ADgroup=Get-SPUser -Web $SiteURL -Limit ALL | Where { $_.IsDomainGroup }
}
echo $ADgroup | Export-Csv "C:\Temp\FileNameGoesHere.csv"
PS1 download is here: https://1drv.ms/u/s!Ag4C3w6EUQIggowvfXrE0Z3tfWKJeA
A lot of you may be getting emails from your sys admins telling you about needing to protect yourself from the POODLE vulnerability. I wanted to post my response back to what I did to bring my servers into compliance.
I used a tool called IISCrypto to place the server in best practice template from the command line. You can do it to be in PCI, PCI31 or FIPS140 compliance as well.
Here’s what I ran for what got fixed:
They also offer a GUI that you can run to see exactly what’s being used. Here’s the box after I applied the command ran above to confirm the removal of PCT 1.0 & SSL 2.0/3.0:
My recommendation would be to deploy the command line version of the tool and execute the best practice template, let it apply the best practice template and restart the box.
However, if you don’t prefer a 3rd party tool then you can follow the Microsoft suggested actions to update the registry entries and build a .reg script to run.
Hope this helps.
The Issue:
After I had updated my .Net Core on my developer machine to a newer version I went to debug a web application I had and received this error:
Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
The Problem:
Here is what I had in my config prior to the update install:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="DotNetOpenAuth.Core" publicKeyToken="2780ccd10d57b246" />
<bindingRedirect oldVersion="1.0.0.0-4.0.0.0" newVersion="4.1.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="DotNetOpenAuth.AspNet" publicKeyToken="2780ccd10d57b246" />
<bindingRedirect oldVersion="1.0.0.0-4.0.0.0" newVersion="4.1.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="EntityFramework" publicKeyToken="b77a5c561934e089" />
<bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
I had outdated references in my config file.
The Solution:
Ensure your references get updated after you update your development environment.
Here is what I updated to:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="DotNetOpenAuth.AspNet" publicKeyToken="2780ccd10d57b246" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.3.0.0" newVersion="4.3.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="DotNetOpenAuth.Core" publicKeyToken="2780ccd10d57b246" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.3.0.0" newVersion="4.3.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="EntityFramework" publicKeyToken="b77a5c561934e089" />
<bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
Hope that helps. Questions are always welcome.
I was recently upgrading a Ubuntu server from 12.04.5 LTS to 14.04.4 LTS and for the most part had a pleasant experience. I’m going to attempt to document my steps I used for the upgrade below and comment to any issues I found (and tips to fix).
sudo apt-get update
Issue: When I first was experimenting on a clone I noticed after running this command I received a bunch of 503s on the apt-get attempt.
Fix: After opening up the firewall to allow outbound traffic to http://us.archive.ubuntu.com then the Get attempts were successful.
sudo do-release-upgrade -d
Tips:
Once the upgrade/removal process is complete you are (usually) prompted to restart the server itself. Should you not be prompted for such you can run the following command to restart the server:
sudo reboot
Now then, you should now have your server up to date and installed. This should mean your web site comes right up without problems, right? Wrong. Chances are you need to go and verify everything still runs after the upgrade. I’ll show what issues I ran into below as proof of that concept.
Issue: All web sites that previously worked before the upgrade now come up with “401 Unauthorized”
Fix: As a part of the Apache2 update in Ubuntu 14.04.4 all of the virtual host files in /etc/apache2/sites-enabled folder have to be updated to have .conf appended to them.
So in this example I had a file called my.website.com that I need to be my.website.com.conf, I made this change using:
cp my.website.com my.website.com.conf
Once I updated all of the files to use .conf related to my web sites I restarted apache2 to enforce the changes:
sudo /etc/init.d/apache2 restart
After this I was able to see my sites as I expect. Now I am seeing some odd error messages at the top…let’s dig a bit more.
Issue: I started getting some unhandled error exceptions (8192) that were in some error handling code
Here was the snippet before I made changes that had the problem:
$errorTypeLookup = array ( E_ERROR => 'PHP Fatal error', E_DB_ERROR => 'Database Error', E_SYSTEM_ERROR => 'System Error', E_SECURITY_ERROR => 'Security Error', E_VISIBLE => 'Warning', E_WARNING => 'PHP Warning', E_PARSE => 'PHP Parse error', E_NOTICE => 'PHP Notice', E_CORE_WARNING => 'PHP Core Warning', E_COMPILE_WARNING => 'PHP Compile Warning', E_USER_WARNING => 'User Warning', E_USER_NOTICE => 'User Notice', E_STRICT => 'PHP Runtime Notice', );
Fix: If you read here about error function contstants you’ll find the introduction of 3-4 newer ones after PHP 5.2. The one in particular that I needed to add (related to 8192) was E_DEPRECATED. After I added it (and a couple others) and restarted apache2 those particular issues went away. Below is my updated snippet:
$errorTypeLookup = array ( E_ERROR => 'PHP Fatal error', E_DB_ERROR => 'Database Error', E_SYSTEM_ERROR => 'System Error', E_SECURITY_ERROR => 'Security Error', E_RECOVERABLE_ERROR => 'Recoverable Error', E_DEPRECATED => 'Deprecated', E_USER_DEPRECATED => 'User Deprecated', E_VISIBLE => 'Warning', E_WARNING => 'PHP Warning', E_PARSE => 'PHP Parse error', E_NOTICE => 'PHP Notice', E_CORE_WARNING => 'PHP Core Warning', E_COMPILE_WARNING => 'PHP Compile Warning', E_USER_WARNING => 'User Warning', E_USER_NOTICE => 'User Notice', E_STRICT => 'PHP Runtime Notice', );
After I worked through these issues my web sites functioned as expected. Please do understand that based on your web sites/apps that these steps and issues/fixes will always be unique. The good thing is that for the most part what is documented on the internet will usually help guide you through particular problems you are facing. I hope this helps, questions are always welcome.
Helpful links:
@JaredMeredith 