Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Richard, I just went through and pre-staged a computer in AD, and created a device collection with an OU query, and a collection variable with a few values of applications. I'm going to see if I run into the same issues with the membership not updating. I believe I may have found a script that might do it, but I don't know if it can do it during OSD. https://gallery.technet.microsoft.com/scriptcenter/ConfigMgr-UpdateRefresh-68041cc7 I'm testing your process myself to see if I encounter the same issues.
  3. Today
  4. If anyone gets an access denied error at the last step (certutil -crl), then please reboot your Issuing CA server once and then issue the command again. I had this issue and apparently several other users had this too per various forums.
  5. Hello, Thank you for your response. I should probably have explained this a little better. We have Device Collections for each faculty, each collection has a collection variable "SA" (Special App), 01, 02, 03 and so on. Each variable represents the name of an Application on SCCM. These collections query their membership based on Active Directory OU... so any new machines which aren't known on the network, can't be discovered in those collections. Cheers, Richard
  6. Richard, If you've manually added the computer objects to an OSD Device Collection, there might be something wrong with one of your applications in you install application step. Have you checked to make sure each application is distributed to the DP? This statement doesn't make sense. The applications you are deploying using the install application step shouldn't be reliant on which collections the computer objects are in, unless you're doing something like this (Separate Task Sequence to deploy applications to a specific collection): If you're deploying applications during OSD, you should have a step similar to this (Install application), that is not reliant upon which device collection the object is in. Also, curious why are you pre-staging computer accounts in AD, is it so you don't have to manually move them to the appropriate OU afterwards?
  7. Another query. If i used the settings as you suggested and used pre cache whether will it download all drivers model or will it download the required model only? I have noticed its downloading all driver models.
  8. Yes you are right. What I meant is we have SP4 drivers which is msi and that we can deploy during post processing apply setup based driver option.
  9. Yesterday
  10. if the batch file is copying the files, then sccm wont perform any throttling. It's essentially like you copying the files manually. As an alternative, use the file location as a package source and you can have sccm download the files into the local cache then run the command to install from there. In that case the download will be throttled. Does that make sense?
  11. Thanks for the quick reply Kilamym, :-). Really appreciated. Throttling on the DP is already there.The package that is being deployed is just a batch script. This script copies a 10mb file from Central SCCM to each machine in the enterprise. Once this is copied i run a task to install from the location. I wanted to see if i can do the file copy from the distribution point instead of central server. Again thanks for your help.
  12. pretty much all computers need drivers, what makes you think the Surface Pro does not ? have you tried deploying it yet ?
  13. Yes. You can throttle package downloads to clients via client settings. You can throttle the bandwidth setting when sending packages to the DP. Right click on the DP, properties and I think it's the last tab. Sorry but I'm not at my desk right now.
  14. Guys, I am new here, just trying to figure out a way to copy files over the WAN without causing outages . I have a folder that i need to copy to a location on all computers in the enterprise. Is there a way i can copy these files to distribution points in SCCM and then copy it using s script to all computers which fall under that particular distribution point? Any help is greatly appreciated.
  15. Thank you. Yes its same but i have selected cm cache as location. Another question what if some model doesn’t need any drivers like SP (we have msi which applied during post processing).whether task sequence will fail?
  16. Hello. We currently have an OSD Task Sequence for deploying Windows 10 Enterprise 1709 to our client machines. This works quite well for existing PCs which are known to AD and SCCM. We have a mixed environment, where we have multiple departments which require their own set of applications. Again, this works well for existing machines. The issue in which I'm being faced with at the moment, is when we introduce new clients to the environment. Due to the design of SCCM with AD System Discovery, new devices are not discovered as there is no DNS entry for those devices. I have done the following - Pre-staged computer accounts on Active Directory. Created computer objects within SCCM with the Name and MAC address of the new devices. Added new objects to the OSD Device Collection for OSD. The problem here is that some Device Collections which have Collection Variables attached, rely on Active Directory OU membership rules. As these machines haven't yet been discovered as such, they don't become members of these collections until the OSD process has finished the installation of the ConfigMgr Client has completed. Once that has completed, the machines then fall into the correct collections, but the Install Applications step within the Task Sequence doesn't complete as the collection variables haven't yet been evaluated. I was wondering if anybody else here has experienced this and maybe have a solution/work around? Would there be any Powershell scripts which could be used to force a re-evaluation on collection variables prior to the Install Applications step? Cheers, Richard
  17. Hi i know this is old post but i have some confusion. I need to add few drivers in our upgrade task sequence. I have created the task sequence but not yet clear about how to give variables in OS installation to install drivers. Only %drivers01% is enough or may i need to create multiple OS installation steps and provide variable accordingly
  18. How about this? No need for packages, or ServiceUI. Run as a command line: powershell.exe -command (new-object -ComObject Microsoft.SMS.TsProgressUI).CloseProgressDialog() ; (new-object -ComObject wscript.shell).Popup('Message Goes Here.',0,'Title Bar Text',0x0 + 0x30) ; Exit 0
  19. Last week
  20. Automatic deployment rule was working perfectly without any issue. In most Recent deployment all workstations and servers stuck at 0% download from last 4 days . Do not find any issue in the logs. Any help will be highly appreciated.
  21. It will not be a permissions issue for SW inv., why because if HW inventory is working then SW inv will work too. So this thread started with SSRS problem and has move the SW inv. so is the SSRS problem fixed? for SW inv, have you confirmed that it is actually being inventoried on a client computer?
  22. Thanks for that, Garth. I was aware of the issues around software inventory, but I think your posts have finally persuaded me to turn it off. However, before I do that, I want to figure out why these tables aren't being populated, and why the permissions seem screwy. I agree that inventorying .exe is rather excessive, but I was trying to mirror the settings on the old server (set up long before my time), which was working perfectly well. Oh and sorry for the misunderstanding; I didn't mean I'd configured it just now. I meant "simply". It's been like that since about October last year. Anyway I'm thinking more and more that this is a fault, and not that I've mis-configured something, so I'm going to try re-installing the reporting point, to see if that fixes it. After that, it's a call to Microsoft. Thanks for your help!
  23. I updated our SCCM deployment to 1810 last week, including installing Hotfix Rollup KB4486457 and Hotfixes KB4490575 and KB4490434. Now we seem to have duplicate user resource objects. The main difference between the two objects is the newly-created object only has the "SMS_AD_USER_DISCOVERY_AGENT" listed in "Agent Name" in the properties of the resource whereas the original object additionally has "Intune_User_Discovery_Agent" listed. Other differences include the "Agent Time (UTC)" property: the new object has a recent timestamp (today) but the original has two timestamps (one from before the upgrade and the other from last year); the "Creation Date (UTC)" property and "Resource ID" are obviously different also. I don't think we've hit this: https://support.microsoft.com/en-gb/help/4490434/duplicate-user-discovery-columns-in-configuration-manager. The SQL query yields no results. One thing that is strange is if I look at the "Updates and Servicing Status" for the last two hotfixes, they both show "Post Installation" as "In progress" despite both having an overall status of "Installed" (see attachment for example). Does anyone know what might have happened and how to fix? Which object should we get rid of and what's the best way to do this in bulk? Many thanks in advance!
  24. I did something now which made it work, not entirely sure how to correct this in the TS. When I booted F12, I used DiskPart to list disk, I cleaned it and created a partition. The deployment was successful after that. So it seems that the TS isn't partitioning the disk the way it should? What can I look at?
  25. Hey guys, In short, I'm trying to figure out if I can streamline automation, and deployment process with our current SCCM (current branch 1802) infrastructure. Long story, we are currently piloting In-Tune. Microsoft pitched it as, "this will cut deployment time down to 10 minutes, or less, and you can pull new devices out of the box and pretty much have them ready to go within that same time frame". After the past month or so of testing, we are finding that's not necessarily the case. Devices need to be in OOBE state and don't always necessarily go through the first pass. When they don't go through, they need to be reset which then adds the lengthy 40-minute time-frame plus the 10 minute provisioning. There also seems to be a lack of information for us to troubleshoot errors (unless this is more of a training issue), which ends up creating many additional calls between Microsoft and our team. We have a functional SCCM environment, with packaged apps, etc. I've seen the MDM option in SCCM, but haven't played with it too much. I believe I should be able to Enroll new OOBE wireless devices similar to the way we would with In-Tune using these tools (but keep the devices on prem). My question is hopefully not too vague, is this process pretty well streamlined in config manager? Is there a way to initiate the same device reset that In-Tune can with newer variants of Windows 10? Each of our techs manages between 1000-2000 devices, so I'm trying to simplify things for them and increase productivity. If you have any insight or experience with testing both of these, please feel free to share. Thanks!
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
  • Create New...