Herwin_D

YPCC and Tregelen, Thank you guys for your clear answers! I've tested with domain join, and came up with the following, I moved the Join domain after install sccm client, Now the variable on the task is working and the server is joined to the domain. So in my TS I got a folder, Join domain, and under there i got all jobs for joining different domains, with different computernames! Wil also look into Tregelen his answer, for setting the variables. Again many thanks!! Herwin

YPCC, At this moment, our patching mechanism is manual with WSUS. it's killing and taking a lot of extra work hours.. So i want to automate that. All new servers are brought up to patch level with WSUS. but I want to use SCCM for it. I need to patch 500 + servers in different time frames, where the servers also rely on eachother (so DB needs to be restarted then the web/app server) etc. So bunch of servers only can be serviced like monday evening, where others only can be serviced friday night. I dont want to have all peeps who create servers, demolish my SCCM environment, by putting servers into collections and forget to take them out.. and when SH*t happens, they blame the SCCM admin :-) (which is me..) I just want to create a nice working environment with all happy admins/users. When you say you have a baseline of patches, a SUG can only contain 1000 records (max) so how do you handle that, for servers, I can offline service the wim file, but for office? do you keep all patches in the baseline? Maybe I'm thinking in a to difficult way, but this is how I see it..

Tregelen, can you please clarify that? On my collection I have the variable OSDComputerName, do I need to put all those other values also there? And if I do, how is it dynamic, do i need to type the whole DC=,ou= etc? i now got on the task in sccm the add condition WMI query: SELECT * FROM Win32_ComputerSystem WHERE Name LIKE "cust1%" then the server needs to be joined to cust1 domain, but I believe the computername is set later, (maybe running in minint-....)

YPCC Thanks for your answer, but in my opinion this does not answer my question, how can choose or force which domain the server is going to belong to. So maybe before the OSD task a menu where to put domain name.

Hello, Next problem I know I'm going to run into: I want to deploy machines with a TS, making a TS and add the computer to a domain is easy. but I want to be able to or choose the domain where the server is going to belong to, or want to that the TS sees the first part of the machine name, and knows to which domain the machine is going to belong to. I know how to set computername before start of OSD, is it also possible to have that kind of input for domain membership? (OSDDomainName or so..) Or have a dropdown list to choose domain Please advice Thanks! Herwin

Hi All, I'm stumbeling with updates, like a lot of people and can't seem find to find a nice working solution. Situation: Multiple schedules to install updates, (say 4 collection with servers with different deadlines and installation times) new servers are NOT build with SCCM, the are deployed using MS Orchestrator to Hyper-V. In the past i was working with only updates which where needed, so my Software update group and my package only contains the needed updates (for that moment that seems the way to keep it simple, but then a new server was added, which needed other updates, so there was a lot of work to get this server up to date. so I've done the following after reading stuff on the internet, and looking at the WSUS we are currently running. Create 1 big deployment package with all updates into it. (takes space, but i'm sure all updates are there when they are needed.) Created 4 Software update groups, 1. all updates before 2013 2. all updates between 2013-2014 3. all updates 2015 4. all updates 2016 (this is appendable, so every month this one expands) The plan i had was the following: deploy 1,2,3 as available to all 4 collections, (My opinion was that when there is a maintenance window the updates are installed but this seems wrong) Now i have acomplished that if a new server is added, the SCCM client needs to be installed. Due to collection queries the new server is added to the right collection, and after a while the updates are available and we can install them. Deploy 4 as required every month. so also new servers are updated. If anybody has a good suggestion to simplify this, please help, i'm running in circles and not seeing the exit at the moment. Also i want to start using SCCM to run the installation of new servers, and want them patched with all updates. So my idea is the following: create task seqence, deploy as available to unknown computers (with password protected) and that way i can service new Servers. now the windows updates, do i need to deploy them (available) to all unknown computers, so when the task sequence is run, the updates are installed, or is it better to manually create a machine, (name and MAC) and put this one in a new collection with all updates available to this collection? Often we need to build multiple servers, so manually is not my first happy end.. Advice would be appreciated. Herwin

You need to deploy the task sequence to a collection and make it required, not available. But be aware all members of that collection will boot into PXE and start the task sequence, after that, when imaging is done, the clients reboots to normal state. When you need to reimage that client, you need to clear required pxe deployments on the record so for testing, create a collection, assign 1 client to this collection, and deploy a required TS.

Anybody got a solution for the mentioned problem? Or does anybody else see this matter happening? It's taking over all disk space, on the site server DP and all other DP's where the package is distributed to.. I can expand the disks, but when having 10 GB of packages and the DP taking over about 100 GB on size.. i don't get this. please help :-)

Peter, Thx you pointed me in the right direction. checked my configuration, did see that the site server had 5 sec delay,. and the dp should react immidiately. I first tested this with shutting down the wds service on the site server, all worked immidiately. So the SCCM config was working properly. When I restarted the WDS service, it went straight away to the site server. So checked my network, and on my network there was an ip helper address configured, with the ip address of the site server.. So all with all, just another configuration error :-) This case is closed!

Hello Rocket Man, I almost know for sure my boundaries are setup right, ip of site server is in 10.0.20.x Client is in IP range 10.8.20 /23 Remote DP has ip addres 10.8.128.x /24 boundarie group setup with 2 ip ranges, 10.8.20.1-10.8.21.254 and 10.8.128.1-10.8.128.254. On the tab references, the site system server is the DP in that subnet. on fast lan (for him thats all fast.) So maybe im missing something?

We are running SCCM2012 R2 version : 5.0.7958.1501 I was looking for SP1 but cannot seem to find and download it... Maybe thats the solution?

Hello, We are running into a problem with distribution points. We got about 10 GB of packages which are distributed to the distributionpoints. one of this package is the update of SCEP anti virus patterns. I have created the automatic deployment rule also found on this site, and used the automatic update (http://www.windows-noob.com/forums/index.php?/topic/6106-using-system-center-2012-configuration-manager-part-6-adding-the-endpoint-protection-role-configure-alerts-and-custom-antimalware-policies/) But now the contentlib folder is piling up with versions. (if i browse the folders there, i see multiple folders with the pattern files, and the ini file tells me a few versions point to that folder, but when there is a change, a new folder is created, patterns are copied and ini file is created) I know if nothing changes then there will be nothing copied, but when there is a new pattern file, the new one is copied to the DP. THe old versions however do nog get deleted in the contentlib folder, consuming now around 90 GB of space... I hope it's clear for what i mean, there are more people on the net running into this issue, but no solution yet. Best Regards Herwin_D

Hello, When i'm installing a new laptop, and start the laptop with PXE, i see the IP adres of the site server (which has pxe enabled distributionpoint role) (where i thought i needed to see the ip address of the distributionpoint. I also installed a distributionpoint in de laptop site, enabled pxe, changed DHCP to point to the distributionpoint. Copied all packages needed in the task sequence to the DP, (also the bootimage used in de task sequence) So the task sequence runs fine. thats not an issue. The issue is that starting from the boot image is slow. when I start the laptop within de same subnet as the site server, i see the dowloading of the bootimage rapidly, when i do the same in de laptop site, the download is slow (taking up more then a minute or 2 to download the image) So in short, it doesn't matter where i start the pxe boot from, I alsways see the ip address of the site server, not the pxe server i think he needs to use. The packages do come from the distribution point. Can anybody clarify this? By the way, very nice site! found a lot of usefull tips and tricks for SCCM! Best regards Herwin