Of course Microsoft offer support. I'm not sure exactly what you mean by 'mission critical documents' but they offer a high level of support for all of their products.
They will create patches for you if you discover a bug which is effecting your systems and, in most cases, this graduates to a KB once they have tested it fully. The turnaround for this type of thing is usually as long as it takes them - in the order of days (not months, and sometimes less) - and in the meantime they will devise a workaround suitable to your environment. I couldn't comment on cost, though it is obviously worth whatever they charge considering how many large companies are onboard.
Microsoft's definition of EOL is that they will no longer patch bugs found in the product, nor will you be able to obtain support either online, via email or telephone. It doesn't begin shutting down servers, though I suspect if you are running any 10 year old hardware it may be well past the due time for you, as the administrator, to begin a hardware refresh cycle. With an Enterprise-level agreement you will not be paying for the copy of 'Windows 2000' or 'Windows 2003" but rather 'x copies of Windows Server OS' so it makes sense that in order to get the full benefit of your licensing you upgrade your operating system and software whenever possible.
I also don't buy your comment that you can only have first-level support for a proprietary product. Using MS as the example we have been, I think you'll find that the majority of people supporting Microsoft systems are Levels 2,3,4+ (whatever 4+ may be).
My experience comes from working in a range of large corporations, both consulting and in-house, where Microsoft was the ONLY option due to the quality of the overall product and support provided on their enterprise products.
Speaking from experience, having two machines with the same SID on a single Domain you will have issues related to the computer account in Active Directory. Remove one of these computers from the Domain and the others will experience Netlogon errors and various other issues as a result.
Although NewSID may no longer be relevant due to lack of Vista/2008/7/2008R2 support, you should always sysprep/generalize to prevent these issues from occuring.
Not too sure why an MS blogger would have this stance, I've seen it numerous times (10+) with my own eyes. The fix is to either perform an offline workgroup join and generate new SID's on all but 1 affected machine, or to remove machines, NewSID all but one, and rejoin the Domain.
Do you remember when the only thing you could get on copper was an analogue dialup signal?
It's much easier to achieve higher speeds with the infrastructure already in place than without it....or you could just move 100m away from your telephone exchange and use as much of your beloved gigabit ethernet as you like.
The only thing you can do is having the software running on one server, then you stop it and start it on the new server. This is what Windows Cluster is doing for you.
That's not true. For clustering of front-end services (ie, IIS) you use NLB which is fully configurable load balancing and fault tolerance.
I would think that this would also largely depend upon what you are using to serve the pages people are going to be accessing. If you are using IIS as a web server (I'm assuming this is not the case) then the NLB component of Windows is already there ready to be turned on. This will provide fault-tolerance and load balancing for the front-end but if you have databases then these will also need redundancy for your service to be HA (MS have failover clusters for this purpose). I've found MS implementations of load-balancing / HA to be simple and effective if they are implemented properly.
When the choice is consistently the lesser of two evils, rather than the election of a deserving party, this becomes difficult. Not to mention compulsory voting, which causes people who don't have a valid opinion to vote out of ignorance.
Forgive me if I have totally missed the point, but daylight savings is not to help construction workers get to the bank is it? Banks also comply to DST so the times they are open relative to the times people work are the same.
The whole idea behind DST is it gives you time to do things after work that are more enjoyable to do in the daylight hours.. walk the dog, do the gardening, get a suntan. None of these activities would apply to the./ reader so I am not surprised to read all the hatred.
I, for one, am not an advocate as all this extra daylight is fading my curtains.
Allows users to complete their software setup without having to provide a product key.
This isn't the case as far as I've experienced if you slipstream existing SP2 media with the latest service pack. Maybe you have to use new SP3 media from MS, who knows.
instead I would have used my cunning to download the latest Britney album to their server in DRM-free MP3 format. And then promptly reported them to themselves.
Probably around the time that you add an extra couple of 100 square metres onto the sun-facing side of your roof so that there's enough surface area to absorb a worthwile amount of energy, or not until they improve the efficiency side of things.
From http://en.wikipedia.org/wiki/Solar_cell "...a solar cell of 12% efficiency with a 100 cm2 (0.01 m2) surface area can be expected to produce approximately 1.2 watts of power."
What management may not realize, however, is that they are already paying a hefty hidden cost by having outdated systems in place
As opposed to hefty upfront costs upgrading hardware and troubleshooting software-related issues on a poorly supported and performing operating system? What about the extra costs involved in paying staff to wait for your brand new Vista computer to do the same thing an XP machine would do in half the time, like boot?
"The increase in security - the inability for users to just simply install stuff, means that you are decreasing the amount of reactive tasks that an administrator has to perform," said Johnson.
Isn't that what restricting Administrative privileges are for? Grandma's XP Home machine has that feature.
I guess there's no point me pasting any more of the article, it sort of speaks for itself.
They will create patches for you if you discover a bug which is effecting your systems and, in most cases, this graduates to a KB once they have tested it fully. The turnaround for this type of thing is usually as long as it takes them - in the order of days (not months, and sometimes less) - and in the meantime they will devise a workaround suitable to your environment. I couldn't comment on cost, though it is obviously worth whatever they charge considering how many large companies are onboard.
Microsoft's definition of EOL is that they will no longer patch bugs found in the product, nor will you be able to obtain support either online, via email or telephone. It doesn't begin shutting down servers, though I suspect if you are running any 10 year old hardware it may be well past the due time for you, as the administrator, to begin a hardware refresh cycle. With an Enterprise-level agreement you will not be paying for the copy of 'Windows 2000' or 'Windows 2003" but rather 'x copies of Windows Server OS' so it makes sense that in order to get the full benefit of your licensing you upgrade your operating system and software whenever possible.
I also don't buy your comment that you can only have first-level support for a proprietary product. Using MS as the example we have been, I think you'll find that the majority of people supporting Microsoft systems are Levels 2,3,4+ (whatever 4+ may be).
My experience comes from working in a range of large corporations, both consulting and in-house, where Microsoft was the ONLY option due to the quality of the overall product and support provided on their enterprise products.
FWIW I use Mac at home.
practises
Speaking from experience, having two machines with the same SID on a single Domain you will have issues related to the computer account in Active Directory. Remove one of these computers from the Domain and the others will experience Netlogon errors and various other issues as a result. Although NewSID may no longer be relevant due to lack of Vista/2008/7/2008R2 support, you should always sysprep /generalize to prevent these issues from occuring.
Not too sure why an MS blogger would have this stance, I've seen it numerous times (10+) with my own eyes. The fix is to either perform an offline workgroup join and generate new SID's on all but 1 affected machine, or to remove machines, NewSID all but one, and rejoin the Domain.
Do you remember when the only thing you could get on copper was an analogue dialup signal? It's much easier to achieve higher speeds with the infrastructure already in place than without it....or you could just move 100m away from your telephone exchange and use as much of your beloved gigabit ethernet as you like.
The only thing you can do is having the software running on one server, then you stop it and start it on the new server. This is what Windows Cluster is doing for you.
That's not true. For clustering of front-end services (ie, IIS) you use NLB which is fully configurable load balancing and fault tolerance.
I would think that this would also largely depend upon what you are using to serve the pages people are going to be accessing. If you are using IIS as a web server (I'm assuming this is not the case) then the NLB component of Windows is already there ready to be turned on. This will provide fault-tolerance and load balancing for the front-end but if you have databases then these will also need redundancy for your service to be HA (MS have failover clusters for this purpose). I've found MS implementations of load-balancing / HA to be simple and effective if they are implemented properly.
Follow the first link. There we go, that wasn't so hard.
Please can somebody tell me where I too can get a copy of Flash, I need to look at redtube NOWWWWWWWW
When the choice is consistently the lesser of two evils, rather than the election of a deserving party, this becomes difficult. Not to mention compulsory voting, which causes people who don't have a valid opinion to vote out of ignorance.
The whole idea behind DST is it gives you time to do things after work that are more enjoyable to do in the daylight hours.. walk the dog, do the gardening, get a suntan. None of these activities would apply to the ./ reader so I am not surprised to read all the hatred.
I, for one, am not an advocate as all this extra daylight is fading my curtains.
Yes the slipstreamed VLK ISO comes to 640MB. That said, my product keys didn't work with it so maybe you need new media.
SP3 is 316MB.
This isn't the case as far as I've experienced if you slipstream existing SP2 media with the latest service pack. Maybe you have to use new SP3 media from MS, who knows.
Tom Cruise is so pissed right now.. sitting at home with 100 IE windows open hitting Refresh All Tabs.
And put China behind it. IPv4 addresses, plenty. Botnet problem, solved.
I wonder what other tasks this technology will provide hands-free options?
Never! This would definitely be a double-blow.
instead I would have used my cunning to download the latest Britney album to their server in DRM-free MP3 format. And then promptly reported them to themselves.
Android is a platform, not a device.
Was this one of your own comedy pieces?
From http://en.wikipedia.org/wiki/Solar_cell "...a solar cell of 12% efficiency with a 100 cm2 (0.01 m2) surface area can be expected to produce approximately 1.2 watts of power."
./ should make an article about this guy - "Elusive single Vista user tracked down to this very website".
Because... it isn't better.
As opposed to hefty upfront costs upgrading hardware and troubleshooting software-related issues on a poorly supported and performing operating system? What about the extra costs involved in paying staff to wait for your brand new Vista computer to do the same thing an XP machine would do in half the time, like boot?
"The increase in security - the inability for users to just simply install stuff, means that you are decreasing the amount of reactive tasks that an administrator has to perform," said Johnson.
Isn't that what restricting Administrative privileges are for? Grandma's XP Home machine has that feature.
I guess there's no point me pasting any more of the article, it sort of speaks for itself.
but I thought Doc only just figured out the 4th.