Jump to content


haribo48

Established Members
  • Posts

    24
  • Joined

  • Last visited

Recent Profile Visitors

1,127 profile views

haribo48's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi All We have upgraded to SCCM 2012 1702 with hotfix KB4019926 installed, everything seems to have installed fine. I am using the pre-production client which appears to be working a treat and turned my attention to OSD task sequences to test the new client on a build. The task sequence is ignoring the pre-production client despite the option "use pre-production client package when available" being ticked and instead installs the current production client. If i change the task sequence option to use the pre-production client instead of the production client it installs fine so the client does seem to work fine in OSD It just doesn't work if i leave the production client as the live client and tick the option to use pre-production client when available. Couldn't see anything in the logs to explain the behaviour Any help would be appreciated, thanks in advance
  2. Morning All, I have a Windows 10 Task Sequence for a standalone laptop which I need to encrypt with Bitlocker as part of the OSD build. The machine encrypts with bitlocker fine but I cannot find a way to export the recovery key either to a network share (with appropriate credentials) or the local disk (to then backup from the device) during the task sequence. Wondering if anyone has managed to get this working or if has to remain a manual step, i'd appreciate any help/advice? thanks in advance,
  3. Hi Deepak, Thanks so much for replying I will take a look at this which will be a good start. What I had in mind was creating the same kind of requirement that Operating system has, see image below. This way I can tie down a requirement based on either a full Office suite (office 2010, office 2013 etc) or individual office products (excel 2010, excel 2013). thanks
  4. Hello We have several applications in our SCCM environment which are for specific versions of Mirosoft Office or in particular Excel. Now that we are moving to installing Office 2016 I need to set requirements on the application, similar to what we currently do for Operating System. Setting a global condition for one version of Excel is fine, however we have Office 2010, Office 2013 on both 32 & 64bit OS versions. Ideally I'd like to have the option of a selection, similar to the built in Operating System requirement where I can click a selection of whatever versions of Office, or an individual product I need. Could someone point me in the right direction of how to set this up please. thank you
  5. Hi All Has anyone used supersedence with Applications? I am happy with the basic process of how supersedence works and how it will now deal with dependant applications that are attached to a main application. We also use our applications in a task sequence and I don't want to, at this stage, disrupt OS deployments. If I set a new application to superseed an old one, will the old application that is still in the task sequence begin to install the new main application? Thanks
  6. Hi Treglen No we dont have any GPO's that would change cache size or location. We don't use GPO for the client installation - we use client push for upgrading existing clients. It's been a while but I think the default cache size is 5GB but ours is set to 15GB as we have a couple of large applications that can be installed overnight. Doing some research it would appear that the settings are a default in the SWDistSchema.mof with the settings below: Location = "C:\\CCM\\Cache"; Size = "250"; Inuse = "0"; NextAvailableId = "0"; This would explain why the location is being set to c:\CCM\Cache with a size of 250kb but doesn't explain why it's being reinstalled using these settings. My guess is it's doing some kind of remediation and self repair but failing to use the settings applied during client install (via OSD or client push)
  7. anyone able to help? We seem to have a problem with clients doing health check then remediating by doing a repair of the client which results in the issue. thanks in advance
  8. Hi there, Make sure under deployment settings you've made the deployment available to configuration manager clients so the deployment shows up in the clients software center (you can if you want select media and PXE). Under User experience, tick allow users to run the program independantly of assignments which if the assignment schedule is set to a future date will allow the user to click install through their software center. They should get two or 3 warnings advising them they are trying to run a OS build. Hope that helps Thanks
  9. Hi All Since we have upgraded our SCCM 2012 config mgr environment to update 1511 and upgraded our clients, first using the auto upgrade which proved problematic and then client push methods quite a few of the clients appear to be failing the client remediation and re-installing, often breaking the client requiring manual intervention. So far approx 150 clients have repaired themselves and utilised default settings contained in the SWDistSchema.mof file on the client machine which set the client cache location to C:\CCM\Cache and a size of just 250mb Reading posts online suggest the problem is present in update 1602. Anyone else experience this and found a fix?
  10. Thanks Treglen for the reply, I'll have a look at PS App Deploy toolkit see what it offers. Thats the thing the software install TS do work, just the first time a machine is added to the device collection and gets the deployment it fails immediately - no content is downloaded and no smsts.log file is created. It appears it doesn't even try to run. If i wait for the default re-run or manually re-run the deployment the TS works 100% of the time, content begins to download and the TS executes.
  11. Hi Everyone, We use task sequences to deploy software applications to machines such as applications that require multiple steps and conditions such as uninstalling previous versions of software based on conditions, reboots and installing new applications. For this topic OSD doesn't play a part as the task sequnce is ran within windows. Since updating SCCM 2012 config manager to 1511 application task sequences that previously worked via direct deployment to either a machine collection or the application catalog (via a powershell script). Since the update the task sequence always fails the first time it is sent to or requested by a client computer, if you wait for the automatic retry or manually re-run the task sequence from software center it always works fine. Appreciate any advice or help? Cheers
  12. Thanks Garth, appreciate the reply I've seen that it's not best practice to install config mgr 2012 onto the OS drive and not something I'd have chosen myself but what i also haven't seen is anything to say if it will cause us problems (performance, redundancy etc) in the future that would warrant us doing a full re-install - most applications have been ready. Thanks in advance
  13. Hi Ath3na Thanks for the reply much appreciated, the primary site server doesn't have the DP role so I don't need to be concerned about moving the content library and shouldn't need to add a DP role anytime soon In my experience it's always been beneficial to install SCCM to a separate dedicated raid volume and I've reviewed the TechNet post for disk configuration http://technet.microsoft.com/en-gb/library/hh846235.aspx and it mentions for configuration manager and database files use separate RAID 10 volumes for best performance.
  14. Hi There, Looking for a bit of advice, relatively new to SCCM 2012 but have experience looking after SCCM 2007 R3. I have inherited a SCCM 2012 R2 configuration manager system which has no CAS, one primary site server (SQL is on box on a dedicated RAID 10 volume) and 6 DP's. All servers are running Windows Server 2012. The issue, the installation of configuration manager on the primary site server has been installed onto the OS volume, it's a RAID 5 volume and the system seems to be running fine with about 150GB free space, though it's still in testing and only has about 10 clients reporting back. The server has enough bays free to setup a dedicated raid 10 volume for configuration manager to reside. From reading the TechNet articles for planning a primary site server it mentions for best performance use Raid 10 for the configuration manager install and SQL. I guess what I'm looking for are options, the system is still in testing no live machines have been migrated over but most of the applications have been created and the system from what I can see is a couple of weeks away from being ready to go live. I guess I'd like to know 1. Will there be a negative impact in terms of performance, scalability (we have 15k clients), resilience etc and would this justify starting over again i.e. wipe the box and a total reinstall - a last resort I hope! 2. It seems madness to me it's been installed on the OS volume, so can it be moved either by doing a back up and restore using config manager once a Raid 10 volume is created on the same primary site server box or could we purchase a new server and use the migration wizard to migrate the installation over and configure it to use the correct volumes. 3. Create a secondary site on a new box with the correct installation on raid volumes and look to promote and replace the current primary site server with this new box 4. Are there any other options that I'm not considering, has anyone any experience of config manager 2012 being installed on the OS volume and suffered negative effects, or has anyone tried to move config manager install off the OS volume? If there's any guides or documentation someone could share I'd be grateful. I would welcome any advice and info about this as soon as possible as I'm confident a decision will need to be made fairly quickly Thank you in advance, please let me know if you need more information Regards
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.