anyweb

and it's another good reason to use Virtual hardware for this type of exercise as you can snapshot at any time

thanks ! I wrote chapter 16 and contributed content to two other chapters enjoy the read

as long as you have configured everything correctly i don't see why not.

the ADR does not push the updates to the clients, it merely makes the policy available to the clients informing them at their next policy update that these definition updates are available, the ADR also places these updates in the Deployment Package on whatever distribution points you selected, if the clients receive that policy and if they have the source selected as Configmgr (amongst others) then they can retrieve the definition updates via ConfigMgr. When you define additional sources you do so for 'failover', plus as ConfigMgr 2012 RTM sync's the sup only once per day and SCEP updates are released at least three times per day you may want to configure the SCEP antimalware client policy to use other source as i explained, good luck

same version, are you trying this on Wireless enabled devices in a place where there are wireless networks ?

is it expired ? blocked ?

you can simply create a step in your task sequence to start a HTA (hypertext application) which itself gives the user options such as Deploy Windows 7 using Configuration Manager or use Ghost (for whatever reason) do you know that you can create full wim backups of your images without using ghost ? and migrate the data too ? see this HTA which does it all (and more) cheers niall

check this link and watch the videos http://www.windows-server-launch.com/Home

have you verified that your PXE certificate is valid ?

maybe you just didnt wait long enough for the updates to get to the dp's ?

today Microsoft launches it's latest Server OS to the general public, Windows Server 2012. it's an online event starting at 8.am Pacific time

sounds like you'd have to edit a custom page to call a webservice if thats what you want to do, which version of MDT are you using and what web services are you using ?

can you show me a screenshot of the status you are referring to exactly you are prompted for start and end dates in order to create a reporting time scale, if you want daily reports emailed to you in reports then first you'll have to enable email ability within Reporting (SQL Server 2008R2 Reporting Services configuration Manager/E-mail Settings) and then click on create subscription and follow the wizard, does that help ? also have you looked at configuring email alerts for endpoint protection as described here ? cheers niall

when i created a package for Visual Studio back in the day, i remember that the prerequisites had to be installed in a certain order, if you didnt install them in the order they wanted the package would fail, the command line to install those three apps if required is>- then install the main msi in conjunction with an MST created for that very purpose vs_setup.MSI ALLUSERS=1 ADDEPLOY=1 /qb! VS2008.mst see here...

and what happens when you open software center ? do you see the completed changes

looks like he was using a mixture of X86 settings in his unattend.xml file but he was using an X64 image they must match and in this case, they did not.

you could also use the BitLocker FrontEnd HTA to do this here http://www.windows-noob.com/forums/index.php?/topic/4811-introducing-the-bitlocker-frontend-hta/

the only thing to think about is if there are any Group Policies pointing to the old WSUS server you'll need to remove them as ConfigMgr will want to control software update delivery

lots of errors in there, can you verify that your management point is working, this link is for cm07 but it works the same way http://technet.microsoft.com/en-us/library/bb932118.aspx and once again, in monitoring, system status, component status, are things looking all green or mostly red ? any obvious issues in there (like management point being dead ?)

have you tried pushing the configuration manager client to the client AFTER upgrading to R3 ?

are the management point and dp configured for HTTP or HTTPS ? what do your component status logs look like (any other obvious problems...)

is it definetly restarting ? when you do run chkdsk are you seeing lots of errors found ? if so consider running a chkdsk 'job' on these systems one week before they are to be migrated, as an idea....

well unless you actually press F12 it should timeout and continue with the next boot device, the hard disc, so is it ? (after displaying the PXE boot menu....)

Introduction During Windows 8 deployments, if you are using wireless capable computers then you’ll most likely have wireless enabled on them by default and this means that the following screen will most likely appear during Windows 8 setup (OOBE). The installation will halt until you pick a wireless network or until you click on the Connect to a wireless network later link. That is great if you want to connect to a wireless network during setup, but not great if you want everything automated, so how do we stop this screen from popping up ? We can create a custom unattend.xml file to change this behavior and the best way of doing this is by using Windows SIM which is a component of the Deployment Tools which in turn is part of the Windows Assessment and Deployment Kit (Windows ADK). So if you havn’t installed the ADK yet, do so now. Step 1. Start Windows SIM Start up Windows SIM located in the start menu on your Server 2012 install or it can be found here on traditional Server 2008R2 start menu The application will appear pretty bland on first start but we’ll change that soon enough Step 2. Select a Windows Image and create a new Answer File Click on File and choose Select Windows Image, browse to the path of your Windows 8 media and select the Install.WIM file located in the sources folder of that media, if it’s the first time you’ve done this you’ll get a message about the Catalog File being missing, answer Yes. Note that you’ll need to be logged on as a local administrator of this machine. Next you’ll see Windows SIM is mounting the image to generate the catalog file and once it’s done mounting the image and generating the catalog file you’ll see your image listed in the Windows Image section of Windows SIM. Now click on the File menu again, and choose New Answer File, this will populate our Answer File Pane with the 7 passes of a Windows Deployment. Step 3. Add our changes to the answer file Expand Components and scroll down the component called amd64_Microsoft-Windows-Shell-Setup_6.2.9200.16384_neutral click on the plus to the left of this component and find a section in it called OOBE (out of box experience), select it. You will note that the settings associated with this section are listed to the right in the OOBE Properties window pane however we cannot do anything with them until we add them to a Pass. Right click on OOBE and choose Add Setting to Pass 7 oobeSystem find the setting HideWirelessSetupInOOBE and click on the drop down menu, select TRUE to hide this. Step 4. Save our Changes to the Answer File And for the purposes of this post, we are done with editing this unattend.xml (however feel free to experiment with the settings listed), click on File and choose Save Answer file as Save the file on your Configuration Manager server in your \\server\sources\os\unattend xml\ folder as HideWirelessSetupInOOBE.xml. (If you are are doing many customizations in your xml name it unattend.xml for simplicity) Step 5. Create a Package in Configuration Manager Now we need to create a package containing this unattend.xml file within Configuration Manager 2012. In the Software Library workspace, select Application Management, Packages, and choose Create Package. fill in some details about the package making sure to select This Package Contains source files and browse to the UNC where you saved your Unattend.xml file earlier. Click next and select Do not create a program (as none is needed) and continue through the wizard to completion. Step 6. Distribute Content Now that our package is made we need to distribute the content to our distribution points otherwise our clients cannot find it. Right click on our newly created package and choose Distribute Content. The Distribute Content wizard appears, select next Add your distribution points by selecting Add, select Distribution Point from the drop down menu and placing a check mark beside any DP you want to include, and then click next through the remainder of this wizard Step 7. Edit your task sequence Now all the steps are in place to edit our task sequence to add our unattend file, so select your Deploy Windows 8 task sequence, right click and choose Edit. and select the Apply Operating Image step, in this step place a checkmark in Use an unattended or sysprep answer file for a custom installation and browse to our previously created package, select the package, click ok and type in the name of our unattend.xml file as in the screenshot below: Click Apply and you are done, try a new deployment and note that you are no longer prompted to Connect to a wireless network during OOBE. cheers niall

did you make your task sequence deployment available or required ??