Xeon is just a marketing name. The Xeon 3400 are identical with the i5-7xx, i7-8xx CPUs, the Xeon 3500 are identical with the i7-9xx CPUs and the Xeon 5500 CPUs are basically i7-9xx with two QPI Links.
For example, this issue also affects als i5 and i7 CPUs.
This is why should read and understand contracts befor you sign them.
If you sign them anway and then bad things happen, this is entirely your fault. The world is not a nice place, where people will hold you hand and make sure you make no mistakes.
If you make such a mistake, shut the fuck up and pay it off like a man. Afterwards, don't make the same mistake again.
Most CPU's use something around 1V. But their power converters are usually fed with 12V. CPUs made in the last 10 years certainly don't require anything near 5V.
All the parts online shops here have at least one or two store locations, were they sell OS-free self-assembled computers. Some of them sell barebone-based laptops, which you could purchase without Windows. All In-Store.
Lenovo also offers all it's laptop with FreeDOS as an OS option, though that's always a BTO option.
First of all, it changes several ways you "normally" administrate Windows systems - you need to use the EBS tools for most of the tasks, for fear of breaking some assistants.
That's the same as with SBS, except SBS setups are usually much less complex, which means using the normal admin tools isn't necessary as much.
Most of the postings there about fixing issues with EBS's automatic integration, which often doesn't work.
Also, look how many steps are necessary to get an SBS 2008 patched up and how much stuff can break during such a procedure. And then you'll need to fix all the stuff that comes pre-broken (BackConnectionHostnames, Sharepoint Search, IIS DCOM permissions, etc.)
Then there is EBS's security server, which comes with a product noone else uses - "Forefront TMG Medium Business Edition", which is basically a 64bit recompile of ISA 2006 that's compatible with Server 2008. This will force you to redesign your entire network around EBS - a mistake that was made with SBS 2003 (though it was optional there, and the option was removed in SBS08).
SBS has several limitations - some of them come from the "everything on one box" design, which is actually what customers want and thus an acceptable drawback.
EBS has the same level of limitations - which is why i don't like it. In my opinion, EBS should be reduced to a "license kit", that contains all of the EBS components at the same price, but leave all the integration and configuration stuff to a VAR, as a one-size-fits-all solution does not work in such environments as it does with SBS.
EBS sucks. Really. It would be nice if you could just buy the bundle of the "full" products at the same price as EBS, but the way EBS is currently structured it's a nightmare.
Even SBS is an extremely complex product to handle, with lots of special cases to consider since a lot comes preintegrated and everything is a slight bit different compared to their standalone counterparts.
And as it is right now, SBS and EBS are outdated - both still ship with Exchange 2007 and WS08 and from what i've heard so far it will take months if not years till we see them both shipping WS08R2 and Exchange 2010.
If the OP is running Microsoft, EBS would be a bad choice.
Well, it's not like i've not got any clashes with out management (or even that of some of our customers), but i've found it to be the better approach to actually talk things through in the hope of getting a better understanding of both parties.
From my technical standpoint, it's very much important that management _exactly_ knows what they're getting for their money. This also means saying "No". Yes, you can lose customers if you don't promise them 99.999999999% availability for 50$ a month, but the real question if you actually wanted those customers in the first place - they may find some idiot which agrees to work with them, but that's their loss.
Even internally, as we also run our internal infrastructure, it's important to say "no" to unreasonable tasks and stupid ideas. Either management trusts you to actually do the job they've hired you to do, or they don't - then you'll need to find a new job.
Yes, but for example management wanting 24/7 2 hour up&running SLA and having hired a single guy with a budget of 800$ will not work - this is important to get sorted out early. Management needs to know what they want and what they'll get.
A lot of Windows software can make virtualization a necessity, since running certain components on the same machine may create an unsupported configuration or be a security nightmare. For example, a Terminal Server and DC on the same machine is a security nightmare.
You know, you could've started with a bit more details - what operating system are you running on the servers? What OS are the clients running? What level of service are you trying to achieve? How many people work in your shop? What's their level of expertise?
If you're asking this on Slashdot now, it means you don't enough experience with this yet - so my first advice would be to get someone involved who does. Someone with many people with lots of experience and knowledge on the platform you work on. This means you'll have backup in case something goes south and your network design will benefit from their experience.
As for other advise, make sure you get the requirements from the higher-ups in writing. Sometimes they have ridiculous ideas regarding they availability they want and how much they're willing to pay for it.
The first questions are: What are your businesses requirements regarding your IT infrastructure? How long can you do business without it? How fast does something need to be restored?
Starting with those requirements, you can start with possible designs that fit those solutions - for example, if the requirement is that a machine must be operational at last a week after a crash, you can build computers from random spare parts and hope that they'll work. If the requirement is that it should be up and running in two days, you will need to buy servers from a Tier 1 vendor like HP or IBM with appropriate service contracts. If the requirement is that everything must be up and running again in 4 hours, you'll need backups, clusters, site resilience, replicated SAN, etc. pp.
The question of Budget comes into play much later.
Funny, as a system administrator the only thing that cleans malware infections is pressing F12 during boot, and then reapply a clean base image. Deleting the users profile, if roaming, is also important.
Doing anything else means you're an unprofessional hack.
I can take my newly purchased Snow Leopard disk and install it on any machine I wanted that was Intel Inside
Yes, but were talking about licensing here, not about technical possibilities.
That said, the Snow Leopard 29$ is an upgrade-only offer. You may use to do a full uninstall, but without an underlying Leopard license, you're unlicensed.
Apple doesn't have a monopoly, so they can do whatever the fuck they want regarding monopoly laws. And that's how it should be.
For example, i could start selling computers that are loaded with a piece of software written by me that just says "hello world", and license the software that it could only be used on the computer it was sold on.
Slashdot Mirror
Xeon is just a marketing name. The Xeon 3400 are identical with the i5-7xx, i7-8xx CPUs, the Xeon 3500 are identical with the i7-9xx CPUs and the Xeon 5500 CPUs are basically i7-9xx with two QPI Links.
For example, this issue also affects als i5 and i7 CPUs.
This is why should read and understand contracts befor you sign them.
If you sign them anway and then bad things happen, this is entirely your fault. The world is not a nice place, where people will hold you hand and make sure you make no mistakes.
If you make such a mistake, shut the fuck up and pay it off like a man. Afterwards, don't make the same mistake again.
Most CPU's use something around 1V. But their power converters are usually fed with 12V. CPUs made in the last 10 years certainly don't require anything near 5V.
I could also use my ThinkPad to bash your head to a bloody pulp, still doesn't mean Lenovo's at fault.
I can only agree. Teamviewer works well, and we even purchased a few licenses for company use.
All the parts online shops here have at least one or two store locations, were they sell OS-free self-assembled computers. Some of them sell barebone-based laptops, which you could purchase without Windows. All In-Store.
Lenovo also offers all it's laptop with FreeDOS as an OS option, though that's always a BTO option.
There's a variety of reasons why i dislike EBS.
First of all, it changes several ways you "normally" administrate Windows systems - you need to use the EBS tools for most of the tasks, for fear of breaking some assistants.
That's the same as with SBS, except SBS setups are usually much less complex, which means using the normal admin tools isn't necessary as much.
To see why this is a giant problem, look at the EBS blog:
http://blogs.technet.com/essentialbusinessserver/default.aspx
Most of the postings there about fixing issues with EBS's automatic integration, which often doesn't work.
Also, look how many steps are necessary to get an SBS 2008 patched up and how much stuff can break during such a procedure. And then you'll need to fix all the stuff that comes pre-broken (BackConnectionHostnames, Sharepoint Search, IIS DCOM permissions, etc.)
Then there is EBS's security server, which comes with a product noone else uses - "Forefront TMG Medium Business Edition", which is basically a 64bit recompile of ISA 2006 that's compatible with Server 2008. This will force you to redesign your entire network around EBS - a mistake that was made with SBS 2003 (though it was optional there, and the option was removed in SBS08).
SBS has several limitations - some of them come from the "everything on one box" design, which is actually what customers want and thus an acceptable drawback.
EBS has the same level of limitations - which is why i don't like it. In my opinion, EBS should be reduced to a "license kit", that contains all of the EBS components at the same price, but leave all the integration and configuration stuff to a VAR, as a one-size-fits-all solution does not work in such environments as it does with SBS.
OCZ sells some in their Vertex line. They're still expensive as fuck.
EBS sucks. Really. It would be nice if you could just buy the bundle of the "full" products at the same price as EBS, but the way EBS is currently structured it's a nightmare.
Even SBS is an extremely complex product to handle, with lots of special cases to consider since a lot comes preintegrated and everything is a slight bit different compared to their standalone counterparts.
And as it is right now, SBS and EBS are outdated - both still ship with Exchange 2007 and WS08 and from what i've heard so far it will take months if not years till we see them both shipping WS08R2 and Exchange 2010.
If the OP is running Microsoft, EBS would be a bad choice.
Well, it's not like i've not got any clashes with out management (or even that of some of our customers), but i've found it to be the better approach to actually talk things through in the hope of getting a better understanding of both parties.
From my technical standpoint, it's very much important that management _exactly_ knows what they're getting for their money. This also means saying "No". Yes, you can lose customers if you don't promise them 99.999999999% availability for 50$ a month, but the real question if you actually wanted those customers in the first place - they may find some idiot which agrees to work with them, but that's their loss.
Even internally, as we also run our internal infrastructure, it's important to say "no" to unreasonable tasks and stupid ideas. Either management trusts you to actually do the job they've hired you to do, or they don't - then you'll need to find a new job.
Yes, but for example management wanting 24/7 2 hour up&running SLA and having hired a single guy with a budget of 800$ will not work - this is important to get sorted out early. Management needs to know what they want and what they'll get.
Virtualization does not automatically imply redundancy, and VM-level high availability will not protect you against application failures.
A lot of Windows software can make virtualization a necessity, since running certain components on the same machine may create an unsupported configuration or be a security nightmare. For example, a Terminal Server and DC on the same machine is a security nightmare.
Again, wrong approach. Ask the higher-ups what kind of availability they want. The cost is derived from their wishes.
You know, you could've started with a bit more details - what operating system are you running on the servers? What OS are the clients running? What level of service are you trying to achieve? How many people work in your shop? What's their level of expertise?
If you're asking this on Slashdot now, it means you don't enough experience with this yet - so my first advice would be to get someone involved who does. Someone with many people with lots of experience and knowledge on the platform you work on. This means you'll have backup in case something goes south and your network design will benefit from their experience.
As for other advise, make sure you get the requirements from the higher-ups in writing. Sometimes they have ridiculous ideas regarding they availability they want and how much they're willing to pay for it.
No, the budget questions comes later.
The first questions are: What are your businesses requirements regarding your IT infrastructure? How long can you do business without it? How fast does something need to be restored?
Starting with those requirements, you can start with possible designs that fit those solutions - for example, if the requirement is that a machine must be operational at last a week after a crash, you can build computers from random spare parts and hope that they'll work. If the requirement is that it should be up and running in two days, you will need to buy servers from a Tier 1 vendor like HP or IBM with appropriate service contracts. If the requirement is that everything must be up and running again in 4 hours, you'll need backups, clusters, site resilience, replicated SAN, etc. pp.
The question of Budget comes into play much later.
Makes perfect sense to me. But if you don't hire someone because they are, for example, a muslim, you're suddenly discriminating again.
Last time i moved, 70% of the appartments i looked at had a "smoking forbidden" clause in their contracts.
There are plenty of worms that infect vulnerable web forums - like PHPbb.
Then you'd need an automated post to get an alibi for killing the witness.
There is: Cost.
Especially if Flash exists and works the same on all browser. Noone is going to switch to something that now requires multiple video formats.
Try exploiting an SMB2 vulnerability from another computer if the Windows firewall is turned on and in "Public" network mode.
Funny, as a system administrator the only thing that cleans malware infections is pressing F12 during boot, and then reapply a clean base image. Deleting the users profile, if roaming, is also important.
Doing anything else means you're an unprofessional hack.
Yes, but were talking about licensing here, not about technical possibilities.
That said, the Snow Leopard 29$ is an upgrade-only offer. You may use to do a full uninstall, but without an underlying Leopard license, you're unlicensed.
Apple doesn't have a monopoly, so they can do whatever the fuck they want regarding monopoly laws. And that's how it should be.
For example, i could start selling computers that are loaded with a piece of software written by me that just says "hello world", and license the software that it could only be used on the computer it was sold on.