| Mikael's profileTech-HeadBlog |  Tools  Help |
|
October 26 Cluster Shared Volumes and iSCSI could be a problemSo you have decided to run Windows Server 2008 R2, using the new Clustered Shared Volumes features and you are going to have a SAN based on iSCSI. Good for you, then you will properly also want to set it up according to best practices, hmm lets see… Two physical servers, with 4 NIC’s that is perfect. I use one NIC for management, one NIC as the Hyper-V network switch and the other two NIC’s as iSCSI NIC’s and as a best practices you bind off everything except for IP on the iSCSI NIC’s THAT WILL MAKE Cluster Shared Volumes to FAIL !!!Microsoft require you to enable the “Microsoft Network Client” and “File and Printer Sharing for Microsoft Networks” on all network that takes part of the cluster, in other words you have two choices here. 1. Do not use the iSCSI NIC’s as “cluster NIC’s”, in other word make sure that they are listed as disabled for cluster use (You cannot use them for Internal or Client use). Bad thing about this is that in that case they cannot be used as heartbeat either. 2. Enable “Microsoft Network Client” and “File and Printer Sharing for Microsoft Networks” on the iSCSI NIC’s, (All NIC’s) bad thing about that is that you will have some traffic on the iSCSI network that is “unwanted”. For some reason there is no KB article that I have found on this little issue, the problem is that it works perfect as long as you do not use the clustered shared volumes and Live Migration, if you just use Quick Migration it works. It is easy to see if there is anything wrong with the configuration, just open c:\clusterstorage\volume1 on one of the nodes, then try to open the same path on the other node. If it freezes up, you know what the problem is. Option one or option two. I usually take option number two There are two other articles about this issue, sorry to say, not in English. Hungarian - http://www.microsoft.com/hun/technet/article/?id=a20a6494-645d-4ee6-993b-f0e341cfdffc If you open the event log, you will find this: Log Name: System October 25 TechEd EMEA – Berlin in NovemberYes, I’ll be there, working in the “Ask The Experts” area, beside me at least five from my company is going to be there, if you have time or any kind of question, please stop by and say “Hi” /mike October 21 MDT 2010 – Things you should know - Part III missed this one!, shame on me and all credits goes to P-O Axelsson and Bosse Törnqvist for letting me know (A beer sometime?) Fixing the “Final Reboot in a LiteTouch scenario” Version IIThis is the built in “Final reboot”, it does provide the basic need of rebooting. Using the “use shutdown in a TS” method gives you the option of adding a reason in the event log and to set the time before it reboots. This method just reboots (And that can be perfect in most scenarios)
so if your customsettings.ini looks like this:
it will reboot after install Have a nice Deployment day October 20 MDT 2010 – Things you should do – Part II have one problem (well there might be more than one problem, but that is beside the point here). Since I have been doing some OS deployment for the last 23 years or so, stuff that I do I take for granted, things that I know must be done, things that I normally never tell people about, I always assume that they know this. Well, here is the truth, they do not… (some do, some don't…) so here it is: Fixing the “Final Reboot in a LiteTouch scenarioSo the machine is done and ready to be used, but hey it has some summary screen here and it is logged on as the local admin, that means that I need to press ok and then reboot and then let the user logon… We fix this by modifying customsettings.ini and by adding a reboot command in the end of the task sequence First step.Using Deployment Workbench, modify the Task Sequence that you would like to fix.
Second step.Add the following to CustomSettings.ini
NOTE: Do not add the “Restart computer” to your task sequence, that will reboot the machine, but it will not end the sequence. That's why we add a “Run a Command Line” task instead. Have a nice Deployment day October 08 Free P2V tool from SysInternals/Microsoft – Download and play with it todayHey, sometimes it just happens and when it does it is normally simple, fun, small, cool and working. I’m talking about when Mark Russinovich and Bryce Cogswell releases new a piece of software. This time they have done a P2V tool called “Disk2vhd v1.0” that is 673kb in a zip archive. So I have just tested it and as expected, works like a charm :-) and it was so easy, just fire it away and select which disk(s) you want to convert to VHDs and you are done. Copy the file into a Virtual XP or Hyper-V, start it and add VMadditions or Integrated Components. Done, you have virtualized your machine. *** snapshot from web *** Runs on:
Disk2vhd is a utility that creates VHD (Virtual Hard Disk - Microsoft’s Virtual Machine disk format) versions of physical disks for use in Microsoft Virtual PC or Microsoft Hyper-V virtual machines (VMs). The difference between Disk2vhd and other physical-to-virtual tools is that you can run Disk2vhd on a system that’s online. Disk2vhd uses Windows’ Volume Snapshot capability, introduced in Windows XP, to create consistent point-in-time snapshots of the volumes you want to include in a conversion. You can even have Disk2vhd create the VHDs on local volumes, even ones being converted (though performance is better when the VHD is on a disk different than ones being converted).
September 30 MDT 2010 - Fix for ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed” problem with MDT 2010Check out this blog post, a common scenario that has a solution now… /mike MDT 2010 - Fix for ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed” problem with MDT 2010Check out this blog post, a common scenario that has a solution now… /mike |
|||||||
|
|
