wede

OK, What I ment was that when you tick the "Client Cache Settings" in the !Client Settings! window, close the setting and the reopen the "Client Settings" windows in the console the "Client Cache Settings" isn't listed as the other settings you have ticked. I have the same behaviour in my Lab and Prod Environment.

I saw this today to, and I had configured the maximum cache size through "Client Cache Settings" but when I tried to changed that setting in the policy it wasn't visible... Do you se it in the client policy?

Sure, Th first time I modified the boot image the Task Sequence completed the step "Setup Windows & Configuration Manager" and after that it stated "Initializing Hardware Devices" and after that "Windows is starting up" and started looping within these messages. The second time around I modified the boot image, I made a copy and used that one. I modified the boot.wim file according to your guide and after that I added only the requiered drivers to be able to boot the winpe within VMware. I started the task sequence and the Task sequence completed the step "Setup Windows & Configuration Manager" and after that the Task Sequence fails with an error visible. I click ok on the error and behind the error popup message there is the window of "Initializing Hardware Devices" and after that "Windows is starting up", and after this the error pops up again. I click ok on the error to finish the TS but behind it the window of "Initializing Hardware Devices" is present and after that "Windows is starting up"....and so it continues in an endless loop: TS error, click ok on error, initializing hardware devices, windows is starting up, TS error...... the only way to end this is to shut down the machine. The only difference between the first time and the second time is the error message of the TS, otherwise same behaviour. Did I manage to explain it? /A

Had some time to try this again today. I downloaded the script again, edited the IP-addresses. Made a copy of the boot-image we are using and added it back again as a new boot image. I the used this copy to use in your guide. I added back the vmware network drivers to the boot image as I was going to test this on a virtual machine within vmware. Same result with a twist, after the step "Setup Windows and Configuration Manager" the TS fails but when clicking ok in the backround the "Initialize hardware" runs and the the error pops up back again. See attached files..... CheckForNetwork_files.zip CheckNetwork.logs.zip

Thx, I'll do that. I'll get back when I have been able to test it again. Hopefully next week.

Sorry, but I have been in meetings during the day that took som more time than I expected... I have to correct my previous statement. When the task sequence loops it loops by saying the following: "Initializing Hardware Devices" and then "Windows is starting up" and again and again....

Hi, Yes, that was the reason for me trying to implement this into the boot image. However the task sequence and the boot image had been working fine on these machine types up until the implementation of the script. No changes have been made in the driver packages for these machine types, and when reverting back to the boot image that I used Before implementing the script there's no problem. So I don't think there's a lack of any network adapters for these machine types. I'll will try set up the boot image with the script again to generate the SMSTS.log file, hopefully I'll can fix it during the day.... /A

Thanks for a very good guide on how to implement this. I had no problems in modifying the boot.wim file and succesfully updated it on the DPs. I started a installation on a virtual machine, VMware machine with Intel E1000 nic, and there were no problems starting the Task Sequence, but after the step: Setup Windows and Configuration Manager the Task Sequence initiates a reboot and after that it halts and loops trying to, At the same time two of my colleagues initiated the installation of, One physical machine, HP 10140 and on one Hyper-V virtual machine, with the same result as me on the virtual machine I was running the TS on. "Windows is starting up" and then "Preparing network connections" over, over and over again.... in an endless loop until I shut down the machine. - I looked through SMSMTS.log, didn't see anything special. - The "Setup Windows and Configuration Manager" step is just after "Install Drivers" and I wonder if this might have anything to do with the problem. - In the script, CheckForNetwork.vbs, it looks for: (description LIKE '%ether%') OR (description LIKE '%network%'), When I look at the description of the NICs on these 3 machines, the descriptuion contains Ethernet and Network. At the moment this is the only thing that I have found different and I wonder if %ether% and %network% might be case sensitive? Any other suggestions? TIA Anderz

Had a similar problem and it was resolved by, 1. Make a copy of the folder C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 2. Delete the original folder C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18

Hi, I also ran in to the error, but on the sccm 2012 rc running with admin account and also running the console as admin gives the error Error: Following computers have not been imported: Name: test MAC Address: 00:21:5A:F7:EF:B8 SMBIOS GUID: Source Computer: Choose Target Collection: All Systems Errors The SMS Provider reported an error.ConfigMgr Error Object:instance of SMS_ExtendedStatus{ Description = "Unable to save changes"; ErrorCode = 2152205056; File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspsite.cpp"; Line = 1286; Operation = "ExecMethod"; ParameterInfo = "SMS_Site"; ProviderName = "WinMgmt"; StatusCode = 2147749889;}; I tried importing another computer with a different MAC-address that starts with 88:AE........and that computer is succesfully imported. I the tried a third computer with a different MAC-address that starts with 00:23... imports ok My collegue then tries to import the computer that gives error and he succesfully imports it with another name. He then deletes it and tries again -> error once again Any ideas on what might be a reason for this?