Jump to content


Stonelion

Established Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stonelion

  • Rank
    Member
  • Birthday 06/01/1971

Profile Information

  • Gender
    Male
  • Location
    Jersey, UK
  1. Hi, I have heard that it was announced at the recent Geek Week in Germany that the SCCM client push account is stored in plain text and is therefore vulnerable. Is anyone able to confirm this as I cannot find anything mentioned on any sites? Apparently Microsoft released some news about it 3 weeks ago but kept it very quiet. Thanks, Andrew
  2. This worked for me, thanks for posting.
  3. Hi, I am trying to find some help with deploying windows server patches to production servers without deploying the current months group of patches. Here is some background - we have one SCCM 2012 R2 CU2 server with integrated WSUS v3.2. We have two groups of servers, one for the test environment and one for the production environment. These groups are patched using ADR's and have been working great (thanks for the documentation you provided on how to set this up). I have deployed the latest patches to the test environment - the easy part. I would also like to deploy all patches apart from the latest months of patches to the production servers, this would give us a months window to check that the latest set of patches won't have a negative impact. i would like to automate this on a monthly basis Does anyone have any suggestions on the best way to achieve the production environment part of the scenario? The rest is working fine. Thanks for your input.
  4. Would you be using WSUS integrated with SCCM? I find the intelligence you get with this combination makes targeting the correct patches to the right machines much easier. The answer to your questions would rely on how you had your WSUS and SCCM set up.
  5. Thanks everyone for all the advice, all very useful, but I still couldn't PXE boot my new machine. I checked the SMS PXE Service Point under Site Status and saw the below: The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned. SMSPXE.log showed: No Boot Action for Device (2119) found I searched for the error and found the below link: http://blogs.technet.com/b/smsandmom/archive/2008/10/02/configmgr-2007-osd-pxe-booting-fails-with-error-no-boot-action-for-device-x-found.aspx Some clever ... cleared out the boot images
  6. Thanks Peter, appreciate the quick reply, I shall look into those options. Regards, Andy
  7. First off I would like to thank you for a great website, I have learnt so much from here. I have SCCM2007 R3 installed on a single site mixed mode, using AD Discovery, with fixed boundaries to local subnets only. The helpdesk here informs me that on a previous install of SCCM2007 administered by my predecessor they had a function whereby at the end of an OSD to a new PC, the final stage brought up a menu where they could choose what extra applications they wished to install, if any. I have been hunting around, trying to find a way to do this, but the service desk says it still isn't right and that building a new PC still takes too much time. Any suggestions would be most welcome, thanks in advance, AndyH... (Still climbing the SCCM mountain).
×
×
  • Create New...