Microsoft Content Management Server

Author

deployment scenarios

linetlte

2004-02-04, 10:47 am

hi,

i would like to know how you setup your servers in an internet environment
what would be the best configuration considering all of us (i guess) have
tight budget on hardware and software...

Development Workstations
MSDN

1 Development Server for central database
MSDN

1 Authoring Server
CMS Enterprise Edition
SQL Server

1 Staging/Testing Server
MSDN

1 Production Server
CMS Standard Edition
SQL Server

Standard Edition is limited to 15 users
what if the users are a group e.g. they share the same NT account to author
their sites

is it ok to use the MSDN on the staging/test server?

is it advisable to have a separate server for SQL Server

thanks

linette

Stefan [MSFT]

2004-02-04, 10:47 am

Hi Linetle,

groups cannot be assigned in standard edition.
Although it would be possible to use the same user account for multiple
authors this would still be a violation of the license agreement.
MSDN can be used for test scenarios (e.g. to verify a hotfix or service pack
or to do load tests) - not as a staging server.

It depends on the expected load whether you would need a separate box for
SQL or not. You should run load tests.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"linetlte" <linette@wpro.who.int> wrote in message
news:#KIzeZz5DHA.1592@TK2MSFTNGP10.phx.gbl...

quote:

> hi,
>
> i would like to know how you setup your servers in an internet environment
> what would be the best configuration considering all of us (i guess) have
> tight budget on hardware and software...
>
> Development Workstations
> MSDN
>
> 1 Development Server for central database
> MSDN
>
> 1 Authoring Server
> CMS Enterprise Edition
> SQL Server
>
> 1 Staging/Testing Server
> MSDN
>
> 1 Production Server
> CMS Standard Edition
> SQL Server
>
> Standard Edition is limited to 15 users
> what if the users are a group e.g. they share the same NT account to

author

quote:

> their sites
>
> is it ok to use the MSDN on the staging/test server?
>
> is it advisable to have a separate server for SQL Server
>
> thanks
>
> linette
>
>

Anonymous

2004-02-04, 10:48 am

Hi,

Stefan, you wrote..

"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message

quote:

> MSDN can be used for test scenarios (e.g. to verify a hotfix or service

pack

quote:

> or to do load tests) - not as a staging server.

Am I right in assuming that you mean 'staging' in the sense of the 'site
stager', that is a machine used by authors to create content that is then
replicated over to the 'live site'.

Sometimes people use the word 'staging' to mean a server that is set up for
'final integration testing' of builds.. so if you just have a 'development'
server and a 'testing/staging' server then you are probably OK to use the
MSDN license right?

--

Also, we are thinking about installing all the code/cms etc on a 'backup
machine' that could be used in the case of hardware failure on the 'live'
machine. Understanding that 'load balancing' and 'redundant failover' would
probably require extra licenes, we were thinking about just having this
other machine switched off and off-line the whole time, meaning that it
would require a manual process to switch over to the 'backup' machine in the
case of a problem with the live.

i realise that you are not a lawyer, but what do you think the chances are
that this would be potential violation of the license agreement to do this??

Thanks

--

Stefan [MSFT]

2004-02-04, 10:48 am

Hi,

no I did not mean site staging.
I thought about a staging server where content from authoring servers gets
consolidated.

Btw. on a development server you do template developerment and site design.
on an authoring server you do authoring.
on a staging server you do content consolidation and verification.
on a publishing server the final content shown to the end user is hosted.

My understanding is that only for the development server the MSDN license
can be used.
Not for the authoring, not for the staging and not for the publishing
server.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Anonymous" <anonymous@ms.com> wrote in message
news:u648dC25DHA.3664@tk2msftngp13.phx.gbl...

quote:

> Hi,
>
> Stefan, you wrote..
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> pack
>
> Am I right in assuming that you mean 'staging' in the sense of the 'site
> stager', that is a machine used by authors to create content that is then
> replicated over to the 'live site'.
>
> Sometimes people use the word 'staging' to mean a server that is set up

for

quote:

> 'final integration testing' of builds.. so if you just have a

'development'

quote:

> server and a 'testing/staging' server then you are probably OK to use the
> MSDN license right?
>
> --
>
> Also, we are thinking about installing all the code/cms etc on a 'backup
> machine' that could be used in the case of hardware failure on the 'live'
> machine. Understanding that 'load balancing' and 'redundant failover'

would

quote:

> probably require extra licenes, we were thinking about just having this
> other machine switched off and off-line the whole time, meaning that it
> would require a manual process to switch over to the 'backup' machine in

the

quote:

> case of a problem with the live.
>
> i realise that you are not a lawyer, but what do you think the chances are
> that this would be potential violation of the license agreement to do

this??

quote:

>
> Thanks
>
> --
>
>
>

linetlte

2004-02-04, 10:48 am

i think my idea of a staging/testing server is like a pre-production server
exactly the same as the production server but only for testing to see if
everything is ok
before copying to the production server

i am concerned of the high cost of implementing MCMS
so i am thinking of having a setup w/ lower costs w/o violating any license

maybe this setup would be ok:

Development Workstations -> MSDN
1 Development Server -> MSDN (centralized db)
1 Authoring Server -> Enterprise Edition (we have lots of
authors/contributors, this will go directly to the Production Server once
we see that Testing Server
is ok)
1 Pre-Production Server/Testing Server -> MSDN (for testing if site is ok)
1 Production Server -> Standard Edition (initially SE only but will be
upgraded depending on web traffic for loadbalancing)

is it possible that from the Authoring Server you 'stage' your site to the
Pre-Production server first to test
then 'stage' it again to the Production Server if ok ?

pls advise
thanks

linette

"Anonymous" <anonymous@ms.com> wrote in message
news:u648dC25DHA.3664@tk2msftngp13.phx.gbl...

quote:

> Hi,
>
> Stefan, you wrote..
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> pack
>
> Am I right in assuming that you mean 'staging' in the sense of the 'site
> stager', that is a machine used by authors to create content that is then
> replicated over to the 'live site'.
>
> Sometimes people use the word 'staging' to mean a server that is set up

for

quote:

> 'final integration testing' of builds.. so if you just have a

'development'

quote:

> server and a 'testing/staging' server then you are probably OK to use the
> MSDN license right?
>
> --
>
> Also, we are thinking about installing all the code/cms etc on a 'backup
> machine' that could be used in the case of hardware failure on the 'live'
> machine. Understanding that 'load balancing' and 'redundant failover'

would

quote:

> probably require extra licenes, we were thinking about just having this
> other machine switched off and off-line the whole time, meaning that it
> would require a manual process to switch over to the 'backup' machine in

the

quote:

> case of a problem with the live.
>
> i realise that you are not a lawyer, but what do you think the chances are
> that this would be potential violation of the license agreement to do

this??

quote:

>
> Thanks
>
> --
>
>
>

Stefan [MSFT]

2004-02-04, 10:48 am

Hi Linette,

I'm not an expert in licensing things.
You should ask your sales representative for details.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"linetlte" <linette@wpro.who.int> wrote in message
news:#9G7xF65DHA.2760@TK2MSFTNGP09.phx.gbl...

quote:

> i think my idea of a staging/testing server is like a pre-production

server

quote:

> exactly the same as the production server but only for testing to see if
> everything is ok
> before copying to the production server
>
> i am concerned of the high cost of implementing MCMS
> so i am thinking of having a setup w/ lower costs w/o violating any

license

quote:

>
> maybe this setup would be ok:
>
> Development Workstations -> MSDN
> 1 Development Server -> MSDN (centralized db)
> 1 Authoring Server -> Enterprise Edition (we have lots of
> authors/contributors, this will go directly to the Production Server once
> we see that Testing Server
> is ok)
> 1 Pre-Production Server/Testing Server -> MSDN (for testing if site is ok)
> 1 Production Server -> Standard Edition (initially SE only but will be
> upgraded depending on web traffic for loadbalancing)
>
> is it possible that from the Authoring Server you 'stage' your site to the
> Pre-Production server first to test
> then 'stage' it again to the Production Server if ok ?
>
> pls advise
> thanks
>
> linette
>
> "Anonymous" <anonymous@ms.com> wrote in message
> news:u648dC25DHA.3664@tk2msftngp13.phx.gbl...
service[QUOTE][color=darkred]
then[QUOTE][color=darkred]
> for
> 'development'
the[QUOTE][color=darkred]
'live'[QUOTE][color=darkred]
> would
> the
are[QUOTE][color=darkred]
> this??
>
>