Rocket Man

Is it just me or is SAGE accounts impossible to package for silent deployment. I have tried endlessly to get past that install shield but to no avail. I mean for such a great piece of software to have such a bad installer beggars belief. Any other software with a bit of work mind you has been accomplished such as Visual studio 2010, DWCS5, photoshop etc....but SAGE is just prooving to be a pain. Has anyone accomplished this yet? Any advice would be greatly appreciated Rocket Man

It is recommended that you have a seperate SQL server for each server. Both SCCM & SCOM are fairly SQL heavy and having ONE SQL server to run both may result in poor performance.

Create a script that checks the time of the PC....point it to the shutdowntool built into windows in the system 32 folder. If a machine is off the evening before and takes the advertisement the next morning it will not shutdown as it will not run the shutdown tool because it is out of the time frame window...surpress the advertisement also so that it remains hidden. So have an advertisement scheduled to shutdown PCs say at 6pm for instance and at 10pm for for example if time>=18 && time <=18.30 then %systemroot%\system32\shutdowntool.exe +++Parameters etc........ end if if time>=22 && time <=22.30 then %systemroot%\system32\shutdowntool.exe +++Parameters etc........ end if You get the gist...the scripting above is just an example which may not work but if you can program a little then im sure you can add onto this to make it work. I would also recommend taking a look at coretech website...they have a nice a little tool for power management Rocket Man

For starters, DHCP options are not needed when the server does not host DHCP, these are only needed if the DHCP service runs on the same server as your WDS. Have you tried an uninstall(remove role)...restart.....reinstall(add role) without deleting the RemoteInstall folder? How do you mean the WDS server was running very slow?? slow at pxe booting machine to pull down boot.wim? at OS install time? If it is the second then maybe something is up with your network and not WDS

Should not cause major concern.......Try remoting controlling to the machines in question, try Program deployment to the machines in question of course try them individually and if the remote session conects and programs deploy to the specified targeted machine then you are good to go, but by all means do have all the machines turned on at the time just to make sure that the Rmc and program deployment works on an individual basis. Check the conflicting records node also, see if it has matched anything. I have a query that looks for duplicate records which works well, sometimes there can be duplicate enteries of the same machine which can cause problems. select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId full join SMS_R_System as s2 on s2.Name = s1.Name where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId Rocket Man

maybe the report is wrong?? Have you used the resource explorer on each machine in question to see if the MAC addresses are coming up as the same??(I doubt they are) I just ran this report and I have approx 8 machines all uniquely named and the MAC address is different, but still this report says they are duplicate even though it is plain to see the MAC addresses are not the same......... on my report anyway... Try resource explorer on each machine and find MAC address to see if they match They are not virtual machines by any chance?? If they are then there is a good chance they could be duplicated, especially after OSD.. Rocket Man

This is because you have not made a copy of the configuration manager client...the default one can not be edited nor can it be used to be deployed...as a matter of fact it serves no purpose really at all, only other than been the first package to be distributed to a newly created remote DP, which it can not be removed from either. in the snippet above you can see the default client package and the created one. the manually created on should have 5.0 All after it and this is the one you use when deploying How did you copy the original client package did you create a pacakge from definition?? You also need to distribute both boot.wims, the x86 and x64 regardless whether you are using x86 or x64 OS version Rocket Man

You could try this... http://robwhitehouse...yment-services/ I know XP is much different when deploying with WDS...but I think if you use these answerfiles and edit them and follow the instructions correctly you will also have an unattended deployment of XP. By the way the way that I accomplished the XP to load was to disable all other images on the server and leaving the XP the only image available, but it did require a few steps of user interaction so it was not fully unattended....and also the win7 boot.wim should boot into the WDS image pool and pick up the images.....so I do not know why it is not pickng up the XP image....it is after all a wim image format of XP. Unfortunately i did not get a chance to try out the above as we rolled out all windows 7 that semester and abolished XP Good luck with it Rocket Man

Update..this one is now sorted..thankfully

Hi Niall I followed your documents religiously......I think it was fine on the primary SUP, but after some time i noticed the service was in an unknown state..... I am only beginning to phase in the remote SUPs now but have hit a dead end as seen above with the snippets. As i have mentioned the syncronizations are still working away on a daily basis and are also successful....if i run a syncronization from SCCM and open up the WSUS console i can see it is syncing, so there is still a connection i think...but i have lost the MSSQL$MICROSOFT##SSEE service???? Puzzled. I did do some digging and I found that others ran into difficulty with WSUS and MSSQL$MICROSOFT##SSEE after a hotfix came down for WSUS(Kb2720211)....This is also installed on my site server and no option to uninstall I now have another problem and it may be related..but not sure.......whenever i do a fresh OSD the targeted client(s) are not automatically enabled for updates, I have to manually go in to windows update on each client and turn on the windows updates...they are however managed by the System Administrator which is the expected state, but not sure about the....having to manually turn them on?? I have also checked the registry settings on all clients with the above symptoms and the registry value tells me that they know to go to the WSUS server for updates...but should the updates not be turned on??? Thanks Rocket Man

Good to hear....i have 390s in my enviornment also and I downloaded the winPE3.0 driver pack from DELL but i think at some stage before this I may have manually added the 390 NIC driver to the boot.wim also...not sure now though....but it boots the 390s regardless.. Just after browsing your previous link....yes this is the driver pack I also downloaded....it is supposed to boot any DELL machine but unfortunately it does not boot specific laptop models.... Rocket Man

I really want to have my remote site server DPs acting as a SUP as i do not want remote clients pulling updtaes across VPNs and I want the remote SUPs syncronising with my Primary site SUP but it has the error as above in the snippet. When I am adding the SUP role to the remote site server DP and I get to the stage to point it to the upstram server it is greyed out, it's as if it does not pick up the SUP above even though this is syncing successfully daily. Anyone?? Rocket man

De-tick the old boot.wim from deploying from PXE server and make sure to tick your new boot.wim to deploy from PXE server...go to administration node ....distribution point properties and content tab....redistribute from here....remove old boot.wims delete old OSD deployment from unknown collection restart wds service(this will flush out the old pxe advertisements) deploy the TS again to unknown computers....see what happens By the way you can use SCCM to inject drivers into boot.wims....by adding the drivers to the server and then selecting your boot.wim and selecting properties and then drivers tab...select the drivers you want to add and update distribution points with new version....also use binary replication if you have lots of remote DPs Was it the Dell winPE3.0 driver pack??? This pack will boot any DELL machine bar a few models of laptops but these can be added individually!! Rocket Man

Ok thanks for that info Peter...i will leave it as is then so. Thanks Rocket Man

Hoping someone can point me in the right direction... My site system volume is rapidly decreasing in free space. I have tried to monitor the directories on it to pin point the exact reason as to why this issue is occurring. I think I may have found the culprit and it is pointing to the SQL ReportServer_log. Each day I am losing approx 3-4GB of space and this log seems to be increasing. Is there any way of removing old logged data from this.....In my enviornment historic reports is not needed... Thanks Rocket Man

No problem deploying now then Rocket Man

Exactly......you have to flush the wds server from old pxe advertisements..by default it flushes itself every 120 mins(i think), so force it by restarting the service.... What do you mean by disable and enable PXE??

But are you trying to PXE boot the same machines you previously were successful with??? ....please be more specific

How did you deploy the pxe....to what collection?? Are you trying to PXE the same machine(s) again??

What is the comms link between site server and Remote DP lke???? Is the firewall off on the windows 7 box??

Run the capture media CD on the baseline machine whilst logged in....(it cannot be on the domain)......Create a network share and share it out to your network access account.....once prompted to run the CD run it and enter in the UNC path to the share you are after creating ( this is where your image will be captured to)...directly below this enter in your network access account credentials in the form of domain\accountname.......password.........then give it a brief description on the next stage and proceed to sysprep. hopefully it will be successful and capture your image to the share...you will be notified when the process is finished. then create an operating system image out of this newly captured image via the software node ......operating systems node...im sure you are familiar with this??? Once the OS image is created...create a new task sequenec...choose create an exsisiting image ( the 1st choice and go through the steps) Once the task sequence is created you can right click and edit it and add software packages...driver packages...command lines etc...... (do get familiar with this process) Then you can deploy this to your collections....if the target machines have already got the client installed it will deploy even if the machines are in windows(it may take a while though, but you can force the process by openeing up the ConfMgr client in the control panel of the target machines and open up the actions tab and run machine policy...this forces the client to retrieve any policies...assignments targeted to it...by default the client is set to pole the site server every hour for new policies (this can be configured in the client settings) If you are using PXE then again this only work if your target machines already have the client...if they dont it will not work (this is true and i hope others see this).....if your machines have no client but are still showing in your all devices collection then simply delete the entries from this collection out of the SCCM database and deploy the Task sequenec to the unknown Computer collection ( again i hope others read this as this is where alot of mistakes are made with PXE not working etc...even though it probably is working correctly, SCCM will not PXE boot a known computer) there are scripts on the web you can get that will prompt the user to enter in a new computer name before the new OS is installed...i would advice you to source these and use 1 of them other wise SCCM will give the machines a strange name..

Yes in the boundaries node i can see both the AD site names and also the IP address subnet, so in other words I have 30 AD site names and 30 IP subnets.... Surely this is not a problem is it?? So to the original query if I have an AD site name boundary called joebloggs.com and the associated subnet to this is 192.x.x.x/20 and I have created a boundary group called joe bloggs boundary group.......can I associate both of these to the boundary group or is either one or the other suffice?? I have no real problems at the moment......i am just using the AD site name at present, but am curious if it is OK to associate the IP subnet also??? Does it benefit in any way??

I have 30 remote sites in my enviornment and i have created 30 Boundary groups and name accordingly. In the Boundaries node on the console I can see both the IP address range of the sites and the site names also. This probably is normal enough as I have specified to find by both. My query is do I need to add both the IP address range and associated site name to the Boundary Group or would one be sufficient, just curious to know if there is any harm in adding both to the boundary group. At the moment i have only associated the site name to the boundary group. Is it of any benefit to also add the associated site name IP address range also or is this just over compicating the situation. Rocket Man

I have installed WSUS on the primary site.......I have now noticed that the windows internal database service MSSQL$Microsoft##ssee is unknown and can not be found in the system services. The WSUS has now got a constant yellow exclamtion mark on it in server management. The strange thing is that it is still syncing successfully on a daily basis according to the SCCM console and the WSUS console. Has anyone had similar issues and is there a simple fix or do I have to uninstall the SUP and reinstall.or do i leave it as it is??? ....the thing is I have quite a few updates downloaded already and all the clients are also reporting to be managed by the system administrator in the windows update panel, even remote clients on different subnets.

yes you are right the capture media is an ISO, which you will burn to CD, run on a live custom built machine and there will be some steps that you will have to initially set for instance the path to your network share where you want the capture image to be captured to....your network access account credentials...it is pretty self explanatory....after this it will sysprep and capture......make sure and choose the boot.wim that you injected the drivers into when creating the capture media. If successful then you can create an operating system image from it which you can deploy to any amount of machines..... the secret to a good deployment is to have the bare minimum of an OS so that it can suit all models and then attach your model specific drivers as needed with WMI queries.... I have just an install.wim and then add all my software packages i:e IE9, java, Adobe FP, SW, Reader, Office etc with desired driver package......... I also have a custom image with the bare essential software installed as above It seems to work fine so far but i do have some problems at some remote sites due to flaky comms links.. The articles provided by anyWeb on this site are very good for learning how to deploy OS, software and fully install SCCM......I have followed them by the book and so far everyting is good, bar just the forementioned... If you need more info drop a post Rocket man