As we get ready to roll this out live I rebuilt the Host servers and had no trouble with Blade1 and the networking and the switches probably because a was there when I did this. So OK I got Blade1 going and the Virtual Servers redid and ready for the live prime time. No biggie I will just redo Blade2 and set things up like the other one. Things was going fine until I got to the point of getting the SAN NICs in the Vlan and trunked. Things was fine but I didn’t realize one little detail. When you trunk your NIC’s in the switch that is what you see the trunk name not the Ports. I fought this and fought this not realizing what was going on and finally had to have Jason come back just to tell me oh yea you got to Pick the Trunk name and add that to the Vlan. Duh!!! Ok see previous post and the line about “KISS” Keep it Simple Stupid.
Til later just Roger
OK keeping with the theme for the day of putting off other work I downloaded the SCVMM 2008 R2 Beta and tried to install this on my 2008 R2 beta HyperV Host server. When it went to install the VMM it keep erroring with ID 205 which refers to either your server name is over 15 characters or ASP.net is running in 32 bit mode. I had seen this error before and have read all the post where they tell you to rename your server to taking it off the domain and rejoining to formatting it and starting over to checking your networking. Which to me seems kind of extreme as the fix is really simple for my problem anyways but the last one was the ticket.
What I did was checked my binding order of the NIC’s in my HyperV host machine and made sure the LAN NIC was at the top of the order. Also on my HyperV NIC I had defined my local router for DNS and I changed that to the Virtual 2008 R2 DC I had running, tried the install again and away it went. Sometimes the simple things are over looked or the problem is over thought. Check your basics I think that is what was mentioned on that post I had read and also it is so true. As a old teacher I had in Electronic Engineering told us. “KISS” Keep it Simple Stupid
Til Later just Roger
I don’t know about any of you out there but I have been busier than busy the last 4 or 5 months and it seems like more than normal. Are you experiencing this in your world or has it been slow for you? I know I was talking to one of our other techs who concentrates more on the networking side and he has been in the same boat as me.
Plus my wife and I are looking into adding onto our house. So add this to my work and there is not a lot of time left in the day and that is not counting the normal everyday things that comes with having 3 boys in the house yet from Plays, Band, Marching Band, Choirs, Track, and whatever thing they have going on and the 4 out on their own that still play into what you have going on and it can be plain nuts at a time. Ok most of the time but it is rather enjoyable keeps you young.
But we are going to Disney World in June for 2 weeks so that is something to look forward to so of course there has been going over the books and things to do and one thing we did was get ourselves a rental town home right outside of Disney world. This saves us the cost of the on-site sleeping arrangements and the ability to come and go pretty much as and when and whatever we please to. Plus we can eat there before adventuring off for the day. I can’t wait for this to get here.
Til Later just Roger
Do you see your customers doing this? I hear about this all the time on how everyone is going to the Cloud. I am sure this will have the ones it works great for and then ones that absolutely say WHAT? I know a lot of customers that like to walk by their server and go there is my data and can look at see it right there it is not somewhere out in the world that they have no control over. I also know there are companies that their connection out is up and down and not a stable connection so how does that work when you are in the middle of something and the Cloud becomes Cloudy or the Cloud itself has troubles.
But what the companies are also looking at is the cost of their hardware and what they can do in the cloud for limiting their costs. But there sure is a lot of talk about that anymore and more and more of the MS stuff coming out is headed that way. Look at the Forefront for Exchange you can have it running on your local Exchange Server or the Forefront for Exchange running in the Cloud protecting your local Exchange Server.
I never thought 12 years ago I would be doing this job I am now so anything is possible here. Takes note to self to check into that Truck Driving training School. Where do you see your customers or clients going?
Til later just Roger
At our retreat they talked about the tough times that the country is seeing and how we need to connect even deeper with our customers. When they start to thinking about opening up and refreshing equipment and addressing needs they have, we are the first they think of not because we have the best price but because we are a trusted person in there lives and business. Someone who actually cares about them and helping them now in these times and afterwards. Arlin handed out a book called the “Go-Giver” and suggested we read it. I brought the book home and sat down and read the book in pretty short order and to me it answered a lot of questions that I have been asked over time on why do your people you support treat you like they do and I really never had a answer to those questions other than the way I treat them. The one thing I see with this is that the people that are dwelling upon just making the sale and themselves and not what it can do for the customer or for us down the road I can see this causing a issue and the ones that are treating the customer as more than that quick sale but someone that when they come to you for the solution to a problem they have and they know you will find the right one for them and also be there afterwards. I would suggest reading the book and you will see what I am talking about. It definitely struck a cord with me.
Til later just Roger
I was working on my ISA in front of a SBS 2008 server and got myself side tracked again. Well I setup a 2008 R2 domain controller running on my 2008 R2 HyperV Server and then seen they had released the beta of Exchange 2010. Ok I thought I wonder if this will run on my test domain and at first glance I found that it wasn’t suppose to be able to. But I keep digging and found a few that had actually set this up on a 2008 R2 server. So ok I setup a member quickly on the domain and installed Exchange 2010 on the the 2008 R2 server. The articles that are out there now that tell you how to setup Exchange 2010 on a 2008 Server that you need to download this update and the Power Shell 2.0 well you don’t have to do those as they are already in 2008 R2 server. But the install went fine and rather straight forward and pretty much like Exchange 2007 installs.
When I got the Exchange installed I got some Access denied errors but I made sure I did this on the Exchange Server and then I could get around in the management just fine.
Disable anonymous auth in IIS on the Power Shell Virtual Directory
set-user yourusername -remotepowershellenabled:$true
and I ran this from the Exchange Power Shell
But from first glance of the Exchange 2010 right now it is pretty much the same look of Exchange 2007. But there has been changes as something was not where I expected them to be but it makes sense. So I will post more on this as I play with this more and see what is all there. One thing I have found is you can text message to your mobile phone from the OWA. Will have to see if that will have any advantages or not.
til Later just Roger
This one has been definitely a adventure in getting up and running. In Part 1 of this I talked about what we had to do with the Teaming with HyperV. Well that wasn’t the end of the adventure as I thought. I had tested the VS Servers by pinging the IP’s which I would get a response from. I also tested browsing the network and Internet access all looked well. What happened though when I added a static IP to the NICs of the VS Servers was I could still ping the world but not go anywhere. I thought OK they work when DHCP handles the addressing so what I did was on the LAN NIC of the IIS Servers I set a reservation for the NIC and assigned the IP that way on the LAN NIC that we wanted and this worked. I could do what I needed to on the network and such so now what to do on the NLB NIC.
I started by googling the NLB setup of a Virtual Server and I came up with MS KB Article 953828. There was a hotfix for the 2008 Servers that would be doing this but nothing for 2003 Server. On this they talked of steps to do after the hotfix so I thought why not give this a shot. So I staticaly set the IP on the NLB NIC and then used the NLB Manager on Blade1 to configured the Load Balancing on the first IIS Server. Once this was done I shut down the IIS Server and on the NIC defined for the NLB in HyperV manager I added the MAC Address of the NLB Cluster IP started the VS Server up and it was working. I am assuming it has something to do with the switching of the Team and also the HyperV Switch and the MAC address of the involved NIC’s in the whole process. That is something to be figured out yet on why I seen this behavior but in the mean time I have things working the way they need to be working.
Til later just Roger
I don’t know about any of you out there if you have noticed this but on the sites I have SBS 2003 or SBS 2008 running you don’t get those calls for support that much anymore? I can give you a classic example on what I am talking about.
My wife’s business has about 18 users and they use to replace their workstations 6 every year so everyone got a new one every 3rd year. That worked well but there was always something and it was not unusual for me to be on-site 2 to 3 times a week with some kind of problem on the workstations or server. They also had a NT 4.0 Server. So we moved to SBS 2000 which gave them email and ISA and a lot more functionality with what they could do but we still had those support calls. So we introduced a Windows 2000 Terminal Server in the Environment and started replacing the workstations with WYSE 1200 devices. This in costs of replacing the workstations alone saved her about 15k to 20k she figured over 3 years and that included the cost of the new TS Server as we moved from the workstations to the WYSE devices just on equipment. This started the trend of me not being on site so much as we got rid of the workstations and moved in the dumb devices. We still had issues with the Servers at times as Windows 2000 goes.
We then upgraded the SBS 2000 server to a SBS 2003 server running ISA and we upgraded the Terminal Server to Windows 2003. When we did this we removed the last of the workstations except for 3 of them as they needed them to be PCs. Big drop in on-site time from 2 to 3 times a week to maybe 1 or twice a month maybe. We replaced the 2003 TS Server with new hardware and that became a very stable server. Then this last November we replaced the SBS 2003 server with SBS 2008 and I haven’t been there since. Now to my bottom line that is not a good thing but to hers that is great as her IT costs are down to nothing. I am sure there will be times where they will have something but for the most part as you can see things have been progressively getting better for the customer. We run HP ML 350’s at her location and I think that is a big help with the servers for server hardware stability.
Too me the adding a TS Server to the Enviroment along with SBS getting better with each new progression has made for a very stable customer experence. I also see this same thing at the other locations I take care of so is it just me and being lucky or is all really becoming that good.
Til Later just Roger
I have a client who wanted his server to be fail-over safe from NIC’s to switches to his HP iSCSI MSA 2012i. We used the HP NIC teaming for the SAN NIC’s and for the HyperV NIC Teaming our first sets of tests went fine and then we started having a problem with the HyperV Servers losing connection to the network. I dug into this and found that this is a known issue with HP NIC Teaming and HyperV. Now what am I going to do to make this work properly? I dug on the web for a while and I found a post on the web from a MS test Engineer. On it he explained how to use the Broadcom Nic Management Suite to use the teaming feature from that and then create your HyperV Networking. Ok I thought what do you ahve to lose here so I set it up. I let the HP Network Management do the SANTeaming and then used the BACS 11.6.10 version do the teaming of the HyperV NIC’s. I got this setup and the Virtual Servers running and started my testing and this worked. No loss of pings or anything here. Looking better so now for the true test if I lose a NOC will they keep working so I unplugged one of the NIC’s and the HyperV Servers keep running like nothing happened. I am now on hour 16 of the test and the VSs are still going no problems.
Til Later just Roger
This week I was on-site at a customers and I had a server as I was watching it blue screen. You know those feelings when this happens but the server came back up OK. So I got to digging and found that this was happening when the server was under a load or doing a shadow copy. So ok what is going on here and I was not really finding anything giving me a clue why. So I dug some more and found the memory.dmp file that the server dumped so ok now what to do. I emailed one of the techs that if anybody had a tool for reading this file he would. Ok his statement was send it to MS it is faster. Now that is fine but they want money so why do that. I went to my friend Google and search for some tools and found the MS Windbg tool and also got the symbols for a 2003 Server. I followed the help for reading the file a dn defined the Symbol File folder and right away when I ran this I seen what was going on. It was a problem with the Storport.sys causing the Blue Screen so I did some searching and found that on some HP Servers running with SAS drives this was a issue and there was a hotfix and I applied this.
But that did not help it did this again so I dug some more and found that some of the HP Management drivers will cause this to happen. The server was one I moved from old hardware to new after the old hardware had died so there could have been some left overs from that so I completely removed the HP Management agents and this straighted this out. Now to find a resolution to get this updated with the HP Stuff and not have this happen. More on that later.
Til Later just Roger