These instructions have been performed on EMC VNXe 3100 but should also be applicable to EMC VNXe 3150 and 3300.
- Login to VNXe Unisphere;
- Settings > More Configuration… > Update Software;
- Click on Obtain Candidate Version Online, you will be redirected to EMC Online Support website where you can download VNXe Operating Environment firmware file to your PC
The file extension is .gpg
If you have an application that you want to run on Windows Server 2012 that requires the .NET Framework 3.5, you will most likely run in to a problem when trying to install it. If you are trying to install .NET Framework 3.5 from the Server Manager GUI, you will see this when installing the feature:
“Do you want to specify an alternate source path? One or more installation selections are missing source files…”
I followed my own article here for upgrading from SQL Evaluation to SQL Standard. I had my Dynamics 2013 environment already stood up and unexpectedly already used for development work.
After the ‘upgrade’ steps, the database appeared to be in (suspect) mode and I didn’t have a backup (but a checkpoint via hyperv at least).
Anyway, I uninstalled the SQL Standard from programs and features. Reinstalled the Evaluation version (which is Enterprise by the way) and ran this script on Microsoft’s support site against the CRM databases.
I then followed my article and the databases successfully stayed in normal operating non-suspect mode.
I recently added some new Windows Server 2012 R2 servers to my environment for a project I’m working on. So far I really like this operating system, and I’m getting used to where everything is. That being said, I have ran into a few issues and one of them is an error I’ve been getting when trying to update these servers from my Windows 2008 R2 WSUS server.
When I check for updates I get an error numbered 800B0001 that looks like this:
To fix this error here is what you have to do:
- On your WSUS server install WSUS-KB2720211-x64 and WSUS-KB2734608-x64
- Open your WSUS management console and manually perform a synchronization
- Next, on your affected servers run the following:
net stop wuauserv
rd /s /q %windir%softwaredistribution
net start wuauserv
The issue should be fixed now. If you have a lot of servers/workstations with this issue you might want to run those commands as a part of a start up script.
I was rebuilding my work’s Windows Server Update Services (WSUS) server the other day, and while configuring it I thought about how nice it would be to automate the cleanup process. You know, decline superseded updates, decline obsolete updates etc.
Normally one would have to do this manually by running the Server Cleanup Wizard, but who has time for that?
I have my script running once a week to free up disk space, and generally optimize our patch deployment process.
The following covers the most common service accounts that need to be setup and their typical permissions in order for MOSS to function properly. Note that each deployment is different, so these accounts may differ based upon individual requirements. There are some additional accounts that you may need for other optional services, but they are not mentioned here.
When you install MOSS (not evaluation copy) part of that process is creating a Shared Service Provider. This is essentially a set of services like User Profile store, Search, BDC, MySites etc… These services can be consumed from one or more SharePoint Web Applications (and other apps outside of SharePoint if you like).
There are several things that you must do before you even insert the SharePoint 2007 CD they are:
- Install Windows 2003 R2 with the latest service pack (2 at time of writing) and all of the latest Windows Updates.
NOTE: Please do not use NewSID to change the SID of the machine if you are using a copy of another VM, this breaks things in SharePoint. My advice is to build Windows from fresh or to use Sysprep if you are using a copy of a VM.
Suppose that your team has just posted their latest quarterly reports to various document libraries on the team site, and you want to back up the site at this critical juncture. Or suppose that your team has been moved to a different group in your organization, so you need to move your team site to another server. You can use Microsoft Office SharePoint Designer 2007 to create a backup copy of a site or subsite, and then re-create that site on the same server or on another server.
AD FS 2.0, out of the box, supports four local authentication types:
Quickly ramp up the reader on requirements and steps to successfully provision a user profile synchronization service. User Profile Service Application setup has been one of the most problematic issues for customers so I hope this will clear up some misconceptions.
An end-to-end walk through on how to configure SharePoint 2010 and ADFS v2 together to use SAML claims authentication. I’ll includes steps and PowerShell scripts to demonstrate and will try and bring all of the pieces together in one big posting.
Normally Update Rollups aren’t important, but this is a feature adding and fix that just cant be ignored…