Jump to content


john.rickard

Established Members
  • Content Count

    16
  • Joined

  • Last visited

  • Days Won

    1

john.rickard last won the day on January 26 2017

john.rickard had the most liked content!

Community Reputation

1 Neutral

About john.rickard

  • Rank
    Member
  • Birthday 03/24/1989

Profile Information

  • Gender
    Male
  • Location
    Cornwall, United Kingdom
  1. FIXED -ish https://www.windows-noob.com/forums/topic/14993-windows-10-1511-showing-as-compliant-in-cb-servicing-plan/
  2. FIXED - ish! https://www.windows-noob.com/forums/topic/14993-windows-10-1511-showing-as-compliant-in-cb-servicing-plan/
  3. Finally seem to have sorted out the issue... It seems once a release becomes CBB, it no longer is shown as CB! I guess Config Mgr assumes machines put into the servicing plan for CB will have updated by the time CBB is made live... Change my deployment to CBB and it all works! Once my testing machines have upgraded now I will put it back to CB and await the next release
  4. Update - I have now found that the servicing plan doesn't see the 1607 update... In the preview pane during Servicing Plan properties, if I remove the filters for Required and Name, a list of updates will come back all for 1511... The 1607 update is listed in "All Windows 10 Updates" page, showing as downloaded and deployed...
  5. Hi everyone We are having a weird issue, which I cannot see the reason why! - I have a Windows 10 Servicing Plan setup for CB deployment to a collection. The plan worked a few months ago when I put one machine into it (if i remember rightly)... However we have just started to look into it a bit more and we're coming back with something odd. We add a machine into the collection, it is picked up by SCCM and shows in the deployment monitoring, but they show as compliant! - One machine is on 1511 and the other is on a very very old release, perhaps the first ever release to public. I have trawled the forums and checked the prereq and post install tasks for previous SCCM updates, they look like they're all done. I found a couple of other forum posts with the same issue, but none which have a fix which works for us... Any help would be much appreciated John
  6. Hi Andrew We are having the same issue, but I don't think ours is product key related, as we've always used Enterprise Edition... Just bumping this post to see if anyone else comes back with anything Thanks John
  7. Morning Yes they are x64 as far as I am aware - I am using the files from the x86_64 folder... Thanks
  8. Hi We are planning a Windows 10 deployment for the not to distant future and I am working on getting a new set of task sequences setup for this, incorporating some of the niggly things we've wanted to do for a long time but haven't had the time or patience. One of those things is setting up the computers BIOS settings to our corporate setup. We are primarily all Dell computers, or varying ages, but the majority will run Dell CCTK commands, which is how we do the settings at the moment post task sequence. I basically followed this article to setup the CCTK part of our task sequence (https://miketerrill.net/2015/08/31/automating-dell-bios-uefi-standards-for-windows-10/). Under a Win PE 10 x86 boot image - I have a CCTK exe which changes the system to remove our standard password and use password. So when the rest of the commands are run (which require the password in the command line) the real password doesn't show in the log files. Another CCTK exe resets the password later. I have now found I need a x64 boot image, so I have done the normal import etc. etc. but the Dell CCTK exe which ran perfectly well under x86 now fails... When I try to run it using the F8 command prompt I get a message saying "Subsystem needed to support the image type is not present" - the exe was made on an x64 machine and should be multi platform. Has anyone else tried this and come up with a similar problem or a solution? Thanks everyone John
  9. Hi Everyone Strange problem we seem to be getting - wonder if anyone else has found the same issue... Standard task sequence for deploying Windows 7 x86 and some standard software, used on 7 remote sites each using a local distribution point One site seems to keep failing, on installing a custom application. Same task sequence works on other sites without issue on same make and model of machine Rebuilt the distribution point onto the same hardware, from Svr2008 up to Svr2012R2 - still failed task sequence Built a new DP as a virtual machine for testing - distributed content needed - failed the task sequence Convert the application to a package and it works fine! - but that seems to be a step backwards, and the TS works without issue at all other sites! Anyone have any ideas on what to look at or try? Thanks John
  10. Hi All, Has anyone ever written a script or report to pull out packages and applications which are not distributed to any DPs? We are wanting to do some cleaning up of our source folder... Thanks John
  11. Thanks Atomic12 Unfortunately the reports which deal with deployments etc seem to all need there to be a deployment present... I basically need a report which lists applications and packages where the deployment count = 0 - for someone with some SQL knowledge it probably wouldnt take long to write, but I wouldnt know where to start... THanks John
  12. Good Morning All, I am no wizard with SQL or even SCCM reporting, I have dabbled but that's about it... I am looking for a report which will tell me which applications, and which programs do not have any deployments? Can anyone help? Thanks John Rickard
  13. Excellent - that works brilliantly... I have just changed it to use my parameter of @CollID and it works a treat... Now playing to add an IP address column Thanks
×
×
  • Create New...