Last post Jan 25, 2007 12:04 PM by ccorkrum
Jan 24, 2007 07:47 AM|Mike7854|LINK
I would become provider/maintainer of asp.net 2.0 hosting.
I need of:
windows server 2003;
And then? what other software are needeed?
Jan 24, 2007 12:16 PM|ccorkrum|LINK
If your just going to host IIS and MS SQL that would be it not utilizing a centralized management architecture.
I would add a 3rd party AV software and something that can back up SQL like Backup Exec and that should do it.
and 3 PC's 1 for DNS, SQL, and IIS and all the provisioning done manually or with a CP like Ensim Pro or Plesk.
Jan 24, 2007 02:39 PM|Mike7854|LINK
Symantec Backup Exec
Ensim Pro or Plesk
3 PC's 1 for DNS, SQL, and IIS
what means? You suggest me to use 3 PC, one for DNS, one for SQL, one for IIS ?
If your just going to host IIS and MS SQL that would be it not utilizing a centralized management architecture
When need to use centralized management architecture?
What centralized management architecture do you suggest me?
Jan 24, 2007 03:15 PM|ccorkrum|LINK
Yes I ment by seperating each service onto a seperate PC.
Centralized Management is using like Windows-based Hosting 4.0 where you have an internal infrastructure to do monitoring and reporting via mom and sql, provision services with mps.
It takes a lot more servers atleast 9 to do a full blown deployment following the guide and many things are left out like antivirus backup and restore etc you could probably consolidate somethings like 1 sql server for mps, mom and data hosting have mpssamplecp/plesk/ensim
on the same machine as your shared iis etc many options.
I'm currently setup as such:
1 mom 2005
1 sql for mps
1 sql for mom 2005
1backup/restore for infrastructure
1 backup/restore for services
thats for a shared managed deployment
goto http://www.microsoft.com/serviceproviders to learn more about Windows-based Hosting and the deployment options available that best suite your needs.
Jan 25, 2007 10:36 AM|Mike7854|LINK
Thanks a lot to have help me.
Jan 25, 2007 10:48 AM|Mike7854|LINK
I'm currently setup as such:
What' s dc ?
Jan 25, 2007 12:04 PM|ccorkrum|LINK
you need 2 for fault tollerance if one goes down the other picks up where it left off.
You could even use clustering for services such as SQL, WINS, DHCP etc 1 machine is the live node and 1 in standby to take over if the master goes down.
A cheap way to do this is stagger services like machine A i have exchange and machine B is a node for A, machine B has SQL and machine A is a node for it.
Both machines would have SQL and Exchange installed but only 1 would be utilized until 1 failed.
This way your not just letting a machine sit and do nothing but either machine can do it all if 1 fails.
If you only had 1 you would not be able to log into machines using domain accounts only local.
It all depends on how you want to manage things and how you want security to be dealt with.