keeop

Hi Anyweb, Set this up ages ago thanks to your great guide and all is working fine. But....should probably have checked sooner but I have only just noticed that.. Looks like the monthly deployment package is over 2Gb in size. It seems that each month's new updates are being added to the same depolyment package. Is this correct behaviour? Wasn't sure it it would add or replace. I guess each monthly's SUG contains the references to that month's updates within the singluar deployment package - is that correct? I guess my concern is really just the sheer size. Are only the required updates pulled down on the client PCs rather than the whole lot before being assessed for requirements? Is there a way to clean up the package/source folder? I guess, for a start, we can get rid of all expired updates from both the package and the source folders? Is there a neat way of doing this? Cheers. Keeop

OK, I've managed to find a workaround for this...... Does seem to be a bug with SCCM. I haven't installed any update roll-ups yet so maybe that will fix it? Anyway, I have set the boot image to be available from the PKG$ share as well as from the standard distribution point access. This now works. The boot image is found and downloaded and after that, SCCM uses the alternative port as it should. Not too much hassle. Cheers. Keeop

Hi All, Having some OS deployment issues. Everything was working fine until I was messing about with the MBAM stuff. Bottom line, where I was just using standard port 80/443 for the SCCM/IIS web site, I am now running this web site on alternative ports. I have set these ports in the the 'Site Properties' section, along with ticking the 'Custom Website' checkbox. All standard SCCM software deployments, updates, policy updates etc. work fine. No problems there. However, when now trying to do a Windows build - either using the TS I created following this post or the HTA one, no joy. Going through the logs it seems that I'm getting a 403 error when trying to access the package on the web server, but for some reason it's still trying to use port 80 during this process. So, I'm getting something like: 'Error downloading file from http://myserver:80/PACKAGE/FileNameto C:\_SMSTaskSequence\FileName etc...' As you can see, it is trying to use port 80 even though an alternate port has been specified in SCCM. What am I missing? Is there anywhere else I need to change this port value for this to work? My only guess is that there's something that needs to be changed in the PXE Boot Image, as at this stage, this is the only thing being 'accessed' - we're pre-SCCM client connectivity so I assume it doesn't know about the alternative port at this point. If I create a new boot image, will that use the new alternative port information? Is that what I maybe need to do? Cheers. Keeop

Think I've got it. Changed the user account used by the application pool and it now seems OK. Time for some proper testing......!! Cheers. Keeop

CustomSettings has been copied directly from your source but, obviously, with the HTTP addresses changed and these are correct so that file should be fine. So, I guess it's the web service. Is there an existing script that I can use to debug what's going on, one that doesn't require parameters for example? Cheers. Keeop

Hi, Get the 'Only First MACADDRESS', then it returns values for the UserDomain and UserID, suppresses Password response and then finishes with: Property ComputerName is now = i.e. blank. Sorry, it's hard for me to show a screen dump at the mo, but I hope you get the idea. Cheers. Keeop

Which one would you like as the actual GetComputerName log doesn't have anything useful in it! If I run the GetComputerName script from the command line, the variable is returned blank. If I run the ChangeComputerName script, admittedly using the RIS web service instead, this does indeed work. I'll try running some more of the Maik Koster actions via command line to see if I can get any working. ....yep, other scripts are returning values so it's something specific to that one. Running the IsKnowntoSCCM script brings back a false though, which seems a tad strange as this machine has had the client installed on it for days, has received all relevant software updates etc. Bizarre. Cheers. Keeop

OK, not getting very far. I'm still not sure why this has stopped working. All the parameter variables seem to be there just the GetComputerName variable is not being generated and returned. Any reason why I can's use OSDComputerName? I'll try the 'change name' function and see if that works but I'm not really sure how to go about debugging this web service - they're quite new to me. Cheers. Keeop

Yeah, that seems to have stopped working - not getting a name from what's showing in the log. Strange as it has been working. OK, I'll try and debug the web service - thanks. Keeop

Hmm, the %GetComputerName% variable is not being set any more. The web service and CustomSettings.ini are still the same so not quite sure why this should no longer be working. I'll have to try some of the other functions and variable and debug. Any ideas? Cheers. Keeop

Nope, user error Hadn't copied the extra HTA scripts to the correct folder so the dependencies were not being found. It's currently running through the TS now..... OK, I'll go through them both side-by-side and pick up any changes. Cheers. Keeop

Hi Anyweb, Just managed to upgrade to R2. I'm having the existing TS bomb out before the HTA dialogue is displayed. I'm still using the 2012 SP1 TS as a base rather than the R2 one. Rather than import the R2 one, as I have made a lot of changes to the existing one, are there any sections in the SP1 TS that could cause this to stop working with R2? Are there specific sections I need to change? If there's not much, could it be possible to highlight these? If there are many differences then I'll bite the bullet and import the R2 version of the TS and start from scratch on it. Cheers. Keeop

OK, setting this to use a 'Custom Website' has resolved the issue. Basically.... Created the new web site - which must be named SMSWEB. Doesn't really matter what physical path this points to as nothing will be stored there - it's all virtual directories Created two custom ports for HTTP and HTTPS Changed the Site properties to use these custom ports as default and removed the standard ones Set the Site properties to use the Custom Website (check the box) Kicked off a Site Reset So far, all looks OK and healthy although coincidentally, I'm battling with a severe lack of disk space/pagefile issues which isn't helping matters! Once I've managed to free up a decent amount of disk space I'll have a proper play so make sure everything is as it should be. Plus, I'm not 100% if I need to change these custom ports anywhere else, like maybe in the client settings? Better take a look........ Cheers. Keeop

Right, so it's the custom action within the MP.msi - CcmCreateIISVirtualDirectories - that's throwing up the error. Now, unfortunately it's a .dll that contains this action so I can' see exactly what it's doing. I can take the action out and then the process does complete. Of course, I am missing the IIS virtual directories and possibly other important stuff. The process then goes on to fail on the BGBIsapi install part - doh! More investigation is required.......... Oh, there was also one WMI error generated on the MP install: Event filter with query "SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA "ccm_siteassignment"" could not be reactivated in namespace "//./ROOT/CCM/Policy/Machine" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected. Is this giving anyone else any thoughts?? Would be most appreciated! Cheers. Keeop

OK, now getting this: [13:57:12] ERROR: Failed to acquire the port lock '0x80070005'. .....instead of these lines from above: [11:46:42] Acquired registry mutex. [11:46:42] Port settings have changed - processing port information. [11:46:42] Processing Port List of WebSite [IIS://LocalHost/W3SVC/1] [11:46:42] Retrieved SSLCertHash from WebSite [IIS://LocalHost/W3SVC/1] All I did was change some permission on the SMS\IIS reg key to add in the machine same with full control. However, after I removed the permission changes, still getting the new, different error. Th error code now indicates some form of permission/access problem. Progress?! Still stuck............. Cheers. Keeop

As a follow up, I think I might have an idea what's going on, thanks to the line from the above log: [11:46:42] Retrieved SSLCertHash from WebSite [IIS://LocalHost/W3SVC/1] I had to renew my IIS certificates recently so the original SCCM 2012 install would have been in the context of the old certificates, whereas the R2 upgrade would see the new ones. Looking at the 'SSLCertHash' property above, I'm guessing that SCCM stores the certificate hashes somewhere and maybe is bombing because these values have changed? Is that feasible? If so, anyone know a way around this or where these hashes maybe stored in relation to SCCM? The only other thing I'm thinking is switching to using a 'Custom Web Site' and that way forcing everything to reinstall all the web components. If this works I should be able to revert back to using the 'Default' web site. However, there's also the possibility of borking more components this way if none of the others like the certificates thing. But, I would have assumed they would have bombed out during the upgrade like the MP did. Cheers. Keeop

Hi, I've finally managed to get with the R2 programme and went for the upgrade yesterday. All seemed to go OK although I did have the same scenario as Morpheus above with some tasks still not in a completed state. Then, on closer inspection a few installs had failed, most notable the mp.msi for installing the Management Point. So, I'm now left with no MP. If I remove and re-add, I get the same failure. The problem seems to be highlighted in the msi install log as: MSI (s) (34:90) [11:46:42:406]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3A20.tmp, Entrypoint: CcmCreateIISVirtualDirectories [11:46:42] Acquired registry mutex. [11:46:42] Port settings have changed - processing port information. [11:46:42] Processing Port List of WebSite [IIS://LocalHost/W3SVC/1] [11:46:42] Retrieved SSLCertHash from WebSite [IIS://LocalHost/W3SVC/1] [11:46:42] ERROR: Failed to configure sms ports '0x800700b7'. [11:46:42] ERROR: Failed to process port information. [11:46:42] @@ERR:25011 MSI (s) (34!7C) [11:46:42:828]: Product: ConfigMgr Management Point -- Error 25011. Setup was unable to process the IIS port settings for SMS The error code is 800700B7 Error 25011. Setup was unable to process the IIS port settings for SMS The error code is 800700B7 CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) So, setup was unable to process the IIS port settings. Anybody got any ideas what this is all about?? The SCCM 2012 SP1 install was working just fine before it was upgraded, so I'm a bit baffled. Everything else seems to be fine - it's just the MP install that's bombing. Any help would be appreciated. Cheers. Keeop

Me bad. Didn't have the USMT folder copied to the Tools! Thanks. Keeop

Yeah, that would be cool. I did have a quick look though, and it looks like imagex is not recommended for this sort of thing - http://support.microsoft.com/kb/935467/en-gb What are your thoughts on that? Could you also please give me your thoughts on the partition stuff in my earlier post too please, as it would help me understand things a lot more. One last thing, I'm now having issues with a step in the HTA: xcopy X86 USMT to USMTbits\X86 Looks like the source location doesn't exist - does this mean I haven't installed the USMT package to the machine? Can you also please clarify why one step uses x86 USMT and another further along uses x64? Cheers. Keeop

Is this in the HTA TS already? If not, I guess I can just put it in before the 'Backup' section. Will I need to do anything with the back up name or does the ZTI script create differently named .wim files itself for each partition? Or, does it just create the one .wim? Looking at restore options now. In your TS I don't think there's an option to just do a full restore from a backed up .wim. Is this a fairly straightforward addition? I'll have a look but you'll better know than me! Also, was just wondering why the additional Windows partition is not being created for non-UEFI installs? Is this system partition created elsewhere in the TS via an MDT script that I have missed? Kind of ties in with my question on 'Recovery' partitions. From what I can tell in the TS, if we have an unformatted disk, the multiple partitions are created for UEFI and the single for standard BIOS. If the disk already has an OS on it, for 'New' installs, a single partition is created - there is no UEFI checking/creation section. For 'Refreshes', the disk structure is left as-is. Guess I need something in between that keeps data partitions, if present, but also creates the Windows system partitions if they're not there, like when upgrading from XP to Win 8. Cheers. Keeop

O OK, setting the variable %OSDisk% before the backup routine does seem to work. I am setting it to D:\ but from the playing around I have done, it doesn't really matter what this is set to - the fact that it is set seems to cause the script to run properly and then query the drives/partitions anyway to pick up the correct drive name. Think I'll do some more playing to back up all found partitions, in that case, so that data drives etc. are backed up too. Which actually leads me on to another question....Do you know, off the top of your head, whether these scripts take recovery partitions in to account? If I were to point the scripts to a laptop to either upgrade the OS or totally reinstall, would the manufacturer's recovery partition remain untouched? I'm guessing no on a 'new computer' install, but what about a 'refresh'? Cheers. Keeop

Everywhere I've looked it says to not install MDT 2013 with SCCM 2012 SP1 - only with R2. So, I don't think I'm going to be able to get away with this. I just need to work out why that backup script is failing. Will do some more digging. Cheers. Keeop

I was running through the sequence to create the updated packages - creating an MDT task sequence in order to create the Tools, Settings etc. packages - but these never got created because of a problem creating the boot images. Do you have 2013 integrated with 2012 SP1 then? Is there another easy way to create the Tools package? Is this the only package that needs updating? Cheers. Keeop

I put it on, went through the steps of recreating all the MDT packages but the create TS bombed straight away having issues finding the boot images. So, I removed it and put 2012 UP1 back on. Just having a tinker with your original TS now to see if I can fudge it. Cheers. Keeop.

Hmm, does this require SCCM 2012 R2? I've installed it but all references are to R2 so I don't think it's right. Cheers. Keeop