If you don’t have a push-type patching solution for your servers, then
sconfig works like a charm for it in my opinion, if you can afford to log
on to each Core server interactively to patch.



By the way, if you do have a third party patching solution, you may want to
first test it. We have a couple of non-production Windows 2008 Core
machines and with our solution, BladeLogic, patching always fails on them.



*From:* [email protected] [mailto:
[email protected]] *On Behalf Of *Damien Solodow
*Sent:* Friday, January 8, 2016 12:57 PM
*To:* [email protected]
*Subject:* [NTSysADM] RE: server core, actual experiences?



Can you sconfig to install them, or let SCCM or the like do it for ya. ;)



DAMIEN SOLODOW

Senior Systems Engineer

317.447.6033 (office)

317.447.6014 (fax)

HARRISON COLLEGE



*From:* [email protected] [
mailto:[email protected] <[email protected]>] *On
Behalf Of *James Rankin
*Sent:* Friday, January 8, 2016 12:56 PM
*To:* [email protected]
*Subject:* [NTSysADM] RE: server core, actual experiences?



How is Server Core with updates? I tried it (a very long time ago!) and
remember it being a bit of a PITA…hopefully may be better now though



*From:* [email protected] [
mailto:[email protected] <[email protected]>] *On
Behalf Of *Damien Solodow
*Sent:* 08 January 2016 16:39
*To:* [email protected]
*Subject:* [NTSysADM] RE: server core, actual experiences?



Yep; the required features/roles all work on core.



DAMIEN SOLODOW

Senior Systems Engineer

317.447.6033 (office)

317.447.6014 (fax)

HARRISON COLLEGE



*From:* [email protected] [
mailto:[email protected] <[email protected]>] *On
Behalf Of *David McSpadden
*Sent:* Friday, January 8, 2016 11:37 AM
*To:* [email protected]
*Subject:* [NTSysADM] RE: server core, actual experiences?



Could you put a SCCM DP on a core?





*From:* [email protected] [
mailto:[email protected] <[email protected]>] *On
Behalf Of *Damien Solodow
*Sent:* Friday, January 8, 2016 11:34 AM
*To:* [email protected]
*Subject:* [NTSysADM] RE: server core, actual experiences?



I’m using it for all our DCs which are just DC, DNS, DHCP. So are our
file/print servers, and a few others.

Core on 2012 and up is a much nicer experience than on 2008 and 2008 R2,
and haven’t had any core-related issues. Backup and AV agents are fine with
it.



DAMIEN SOLODOW

Senior Systems Engineer

317.447.6033 (office)

317.447.6014 (fax)

HARRISON COLLEGE



*From:* [email protected] [
mailto:[email protected] <[email protected]>] *On
Behalf Of *Ryan Shugart
*Sent:* Friday, January 8, 2016 11:21 AM
*To:* [email protected]
*Subject:* [NTSysADM] server core, actual experiences?



Hi:

        One of the things I’m looking at doing in 2016 is migrating our
domain controlers, currently about 38 Server 2008R2 around the world, to
2012R2.  Our DCs are just DCs, DNS  and DHCP servers, I keep as much 3RD
party software off of them as I can.  I’m really considering using server
core for all but a couple DCs, as I manage most of them remotely anyway and
the AD Powershell module seems pretty full featured in 2012R2.  I’ve seen a
lot from MS on server core, but haven’t seen as much from people using it
in the wild in large scale deployments.  Does it mainly work as
advertised?  Any got yas other than the obvious 3RD party software issue?
If you’re not using it, why not?

Ryan



Ryan Shugart

Windows System Administrator

MiTek USA, MiTek Denver

303-723-4975




MiTek Holdings, Inc., 2011-2014, All Rights Reserved

*  ________________________________  *

This communication (including any attachments) contains information which
is confidential and may also be privileged. It is for the exclusive use of
the intended recipient(s). If you are not the intended recipient(s), please
note that any distribution, copying, or use of this communication or the
information in it is strictly prohibited. If you have received this
communication in error, please notify the sender immediately and then
destroy any copies of it.

This e-mail and any files transmitted with it are property of Indiana
Members Credit Union, are confidential, and are intended solely for the use
of the individual or entity to whom this e-mail is addressed. If you are
not one of the named recipient(s) or otherwise have reason to believe that
you have received this message in error, please notify the sender and
delete this message immediately from your computer. Any other use,
retention, dissemination, forwarding, printing, or copying of this email is
strictly prohibited.



Please consider the environment before printing this email.

Reply via email to