Application Deployment Architecture - Opinions


hello all, first posting on forums, i'm not sure if i've placed in correct forum couldn't find looking for.

i'm interested in opinions application deployment architecture... more specifically... thoughts on deploying applications in domain efficiently, while trying reduce server sprawl.  nice have seperate server every server-based application, put strain on resources on time... best practices around consolidation?  keep application "types" grouped together?  ie. web based vs desktop applications?  or group based on applications themselves?

for example - i'm looking deploy new "help desk" software suite includes need database server, application server , web server.  database servers clear , easy me architect, should seperate web , application servers other, similar web , application servers?  or should group these (perhaps deploying them same server) because same solution.

i can see pros , cons both methods , feeling going preference based answer, i'm curious if there best practices offer or refer me to.

thanks!

hi,

 

according description, can use categories makes easier users find application in add or remove programs in control panel.

 

i share following microsoft technet article regarding software installation group policy.

 

best practices group policy software installation

http://technet.microsoft.com/en-us/library/cc778924(v=ws.10).aspx

 

regards,

 

arthur li

 technet subscriber support  in forum

if have feedback on our support, please contact  tngfb@microsoft.com . 


please remember click “mark answer” on post helps you, , click “unmark answer” if marked post not answer question. can beneficial other community members reading thread.


Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...