IT Consultant Everyday Notes

Just some problems/solutions storage

Category Archives: 2012

2012 R2: File Server Cluster migration (mounting points disappear)

 

I helped one of our Customers with a File Server Cluster migration. The procedure is described in https://777notes.wordpress.com/2013/12/13/server-2012-r2-file-server-cluster-migration/

The source Cluster was 2008 R2 and were migrating to 2012 R2. backend storage – 3PAR. It was ~50 LUNs to migrate and some of them were connected as mounting points to save letters (see more: http://technet.microsoft.com/en-us/library/cc938934.aspx)

After migration we saw some mounting points disappeared. It turned out the mounting point folders got Hidden and System attributes assigned for some reasons. An attempt to reset the attributes was unsuccessful. Attrib command finished without errors, but attributes remained assigned Smile

In order to fix the situation we needed to unmount the mounting point, use attrib –S –H <<folder>>  to clear attributes and mount the point back to the folder. That brought the mounting points back to (visible) life.

2012 R2 Cluster: “Validate Storage Spaces Persistent Reservation” test failed with warning

 

I recently installed a Failover Cluster on two 2012 R2 nodes with 3PAR SAN storage. Cluster verification tool failed with a single abovementioned warning. Drilling down to the report I found:

Failure. Persistent Reservation not present on Test Disk 0 from node <<MY_SERVER_FQDN>> after successful call to update reservation holder’s registration key 0xb.

Test Disk 0 does not support SCSI-3 Persistent Reservations commands needed to support clustered Storage Pools. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.

Important to note the validation failed in “Validate Storage Spaces Persistent Reservation” test. Google search brought an article from Microsoft  Clustering Team Blog: http://blogs.msdn.com/b/clustering/archive/2013/05/24/10421247.aspx

The bottom line: if you are not planning to use Storage Spaces (introduced with Server 2012) in your cluster – the warning can be safely ignored. Otherwise storage firmware and drivers should be updated.

 

Here is a quote from the article:

“Question:  What should I do when I get this warning?

Check the disks that are identified in the warning message and verify whether you will ever want to use those disks with Storage Spaces.

If you want to use the disks with Storage Spaces on the cluster, then you should check your storage configuration and documentation to see if there are settings or firmware/driver versions required to support clustered storage spaces.  

If you aren’t going to use Storage Spaces with this cluster and storage, and the other storage validation tests indicate the tests passed, then you can ignore this warning.”

Server 2012 R2: File Server Cluster Migration

 

I need to migrate a File Server hosted by Windows 2008 R2 Storage Server to a new 2012 R2 cluster

This GUIDE was used as informational base.

NOTE: In my test environment I do not have mount points on clustered disks so I am not sure if that scenario will work.

I have two 2008 R2 Storage Servers clustered with a File Server Clustered Resource set:

image

I can access the shares:

image

For test purposes I added a user to Share permissions and customized rights

image

 

I also built a fresh 2012 R2 Cluster (without File Server Role)

image

 

Migration:

0. In AD check the Cluster accounts have full rights to File Server accounts. Especially 2012 Cluster account to 2008 File Server Account. I.e. if my 2012 Cluster name is demvhvw12cl and my 2008 File Server Cluster called demvhvw2k8cfs I provide Full rights to demvhvw12cl  on demvhvw2k8cfs

image

1. Microsoft recommends to check if Cluster networks are configured properly – there is no Cluster communication on Storage network, for Example:

2008 Cluster:

image

 

2012 Cluster:

image

2. Start Migration Wizard from 2012 Cluster:

image

3. Select cluster to migrate FROM

image

4.  Select a role to migrate (you can take a look at Reports to see what can be migrated)

image

5. Verify configuration and start migration

image

6.

image

7. Check if migration was successful (use “View Report” button)

image

8. Put File Server role OFFLINE on W2k8 Cluster (source cluster)

image

image

9. Disconnect data LUNs from the source Cluster and connect them to the new one:

I am using ISCSI on W2k12 Server. On the screenshot it is reconnected to 2012 Cluster nodes:

image

Refresh ISCSI initiator on all nodes of W2k8 Cluster and 2012 Cluster and Connect LUNs to 2012 nodes (to ALL nodes!):

2008 Cluster nodes should look like:

image

2012 nodes:

image

10. Check what 2012 node is File Server Role owner

image

and bring connected LUNs online (all Data LUNs) on that machine (from Computer Management/Disk MAangement:

image

image

11. Start File Server Role on 2012 Cluster (right-click – Start Role):

image

12. Check the disk resources and shares are available:

File Server Name resource and IP address should be migrated

image

13. Check if custom permissions are migrated (right-click the test Share and go to Properties/Permissions)

image

14. Try to connect to the share from a test machine to be sure File Server is up and running on the new Cluster:

Auto-fill is working (good sign):

image

and files are there:

image

15. Remove File Server Resource from the old Cluster:

image

Server 2012: RDS deployment failed with: “Unable to connect to the server by using windows powershell remoting”

I tried to install an RDS on one of my 2012 servers.

Installed Session host and WEB server for Remote Apps using Sever manager-Add Role-RDS (that was a bad idea;  you need to use a separate Wizard from “Add Roles and Features Wizard”, not just add RDS role)

image 

After that I figured out I do not have management tools for RDS Smile

So I started the required Wizard. It tried to install Broker and failed with the above mentioned error.

I double checked I have Enable-PSRemoting ran. Still the same error.

I found a thread discussing the issue (http://social.technet.microsoft.com/Forums/en-US/winserver8setup/thread/bbb7427b-f839-48c4-b49c-467138f94b16) one of posts (not marked as an answer) says:

After working for weeks with M$ Support level 2 and higher on this issue below is the fix and reason for the issue.

In a PS Shell

Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000

then reboot

The default remote shell is allotted 150MB of memory. If we have Sharepoint/IIS App pool on the server then this memory is not sufficient to create a remote session (This is used mostly while installing any roles on windows server 2012) . Therefore by running that command we have enabled the remote shell to use 1000mb which will  provide more memory  to windows powershell to make remote sessions and resolve the issue.

I tried that and still got the error (but maybe it was a part of resolution).

After that I thought about my environment – I have two forests with two-way trust between them and I use my “management forest account” which is domain admin in the “demo” forest where I am installing the RDS. I decided to use an account from the “demo” forest instead and successfully installed RDS at this time.

Resolution:

Use admin account from the same forest were I installed RDS. Foreign forest account did not work regardless two–way trusts and admin permissions in the target domain.

Server 2012 PKI and XP compatibility

When your issuing CA is a nice and shiny Server 2012 your XP machines won’t be able to enroll for certificates.

You need to relax security as described in http://social.technet.microsoft.com/wiki/contents/articles/6289.certification-authority-authentication-level-incompatible-with-windows-xp.aspx

certutil -setreg CA\InterfaceFlags -IF_ENFORCEENCRYPTICERTREQUEST
net stop certsvc & net start certsvc

So it is your choice – lower security level or migrate to Windows 7/8.  XP support will end at April of 2014. Winking smile

SCCM 2007: Support for Windows 8 and Server 2012

Server 2012: Hyper-V on Gigabyte P67X-3DR

I am updating my home Lab to Server 2012. As a part of upgrade one of my Hyper-V hosts got the new OS. As soon as I enabled Hyper-V role it rebooted and sit forever showing me nice new windows logo (no logon screen).

 

I found resolution here. USB3 controller should be disabled in BIOS. Hopefully Gigabyte will fix it in later BIOS updates.

From this forum it looks like Windows 8 with Hyper-V role is affected too!

Server 2012: Remote Desktop access–“Insert smart card”

Issue: You try to RDP to a Windows Server 2012. There is no place to type a password on Logon page. There is a message “Insert smart card” instead even though Smart Card authentication is not configured.

Resolution: Log on locally with Administrator credentials. Remove profile of the user you logged on as. Try to RDP again to recreate the profile.

 

Note: it looks like the issue occurres only if you logged with your account locally first. Account with profile created during RDP session are not affected.

Server 2012: Failover Cluster configuration – HA File Share cannot see source path

File Server is one of the roles for Microsoft Failover Cluster. There is a convenient GUI wizard to add and configure the role.

Issue: When you create an HA share on File Server Cluster resource you cannot add any path to host it.

Resolution: Either run Failover Cluster management console from the node currently hosting File Server resource storage, or move the File Server resource to get Failover Cluster Management Console and the storage on the same node.

Note: I observed the issue on a full GUI version of the Server, interesting how it works with core and remote console?

PowerShell 3: Install PowerShell Web Access

1. Install feature (here and after all commands in PowerShell console started “As Administrator”!):

Install-WindowsFeature –Name WindowsPowerShellWebAccess –ComputerName <computer_name> IncludeManagementTools –Restart

image

2. Enable PS remoting (if it is not enabled)

Enable-PSRemoting –force

image

3. Configure PSWA using:

Install-PswaWebApplication –UseTestCertificate.

image

4. Add Authorization rule:

image

5. Verify PSWA using access to /pswa">/pswa">https://<server_name>/pswa from Internet Explorer.

image

6. Use PSWA

image

detailed instruction: at Technet site