anyweb

that should work ok, however measuring compliance on that ADR will be more challenging as you are mixing updates in the same ADR, if you dont care about compliance and reporting then you should be ok, or if you think 'general' compliance is good enough. Normally with servers you want to have a clear picture of what servers are patched (compliant) versus those that are not, in addition to the above, the Configuration Manager client knows which software updates to isntall even if you offer it windows updates from another OS altogether.

if pxe boot aborts then you need to clear the last PXE boot on that computer object in the console (right click,..) as regards "Failed to resolve selected task sequence dependencies. Code(0×80040104)" you need to examine the SMSTS.log file and find out what package(s) are not on the distribution points and once done resolve them

Introduction Backing up your Configuration Manager hierarchy is important for a variety of reasons including: preparation for avoiding loss of data preparation for upgrade failure and ability for site rollback preparation for hardware failure If you don’t enable the site maintenance backup site server task then you will have no site backup to recover in the case of a hardware or other catastrophic failure (by default it is not enabled). It is important to backup regularly on a schedule and to store those backups on another server in case the Configuration Manager site server itself has a hardware failure. Thankfully the site maintenance task called Backup site server makes this easy to do. Step 1. Enable the Site maintenance Backup task Our first task is to enable the built in site backup task in site maintenance. In the Administration workplace, expand Site Configuration and select sites and select your Primary site server that you want to backup, in the ribbon click on Settings and then click on Site Maintenance like in the screenshot below. A list of Maintenance tasks appears, select Backup Site server and click on Edit below to enable the task. Next we need to enable the task, so place a check mark in the box provided Next you need to choose where to store the backup, click on Set Paths and browse to a network path (recommended) or local drive on the site server (not recommended due to hardware failure) to store the site data and site database backup. On my networked server chosen to store the backups I’ve created a share called ConfigMgrBackups with sub folders in it named after the site code of the Primary site servers eg: \\ad1\ConfigMgrBackups\CAS \\ad1\ConfigMgrBackups\P01 \\ad1\ConfigMgrBackups\P02 \\ad1\ConfigMgrBackups\P03 and I’ve give the computer account of the site server Write permissions of that share. Note: The computer account of the site server and the computer account of the SQL Server, if SQL Server is installed on another computer, must have Write NTFS and share permissions to the shared network folder. Next decide when you want the backup task to take place, choose what is appropriate for your environment and try to minimize network bandwidth interruption during office hours by scheduling the backup task during non-business hours. This is a recommended best practice approach. Note: As a best practice, consider a backup schedule that is outside active working hours. If you have a hierarchy, consider a schedule that runs at least two times a week to ensure maximum data retention in the event of site failure. In my example below I am backing up on a Wednesday and Saturday and the backup task starts after 2am and before 5am. If you want to be alerted when a site backup fails then place a check mark in the appropriate box. Click on Apply to apply the changes and then Ok to close this window, you will see that the Backup Site Server task is now listed as enabled in Site Maintenance. Step 2. Manually start a Site Backup In order to verify our backup is working properly, we could wait until the scheduled time, or we could trigger it manually. To speed things up we want to manually trigger the task, to do this open up Services.msc on your primary server and locate the SMS_SITE_BACKUP service, it’s listed as Manual and not started, right click the service and choose start. While the backup task is running we can review the appropriate log and that is Smsbkup.log. In <ConfigMgrInstallationFolder>\Logs, review Smsbkup.log for warnings and errors. When the site backup is completed successfully, you should see Backup completed with a timestamp and message ID STATMSG: ID=5035. Below you can see the Smsbkup.log file open in CMtrace during the SMS_SITE_BACKUP process. Step 3. Verify backup completed successfully Once the backup is complete look for the following line in your Smsbkup.log file along with the STATMSG 5035: Backup Completed - Sun Feb 03, 13:49:21, 2013 And on our network server you can see the following files have populated in our share Success ! Step 4. Archiving your backupAfter successfully backing up the site, the Backup Site Server task automatically attempts to run a file that is named AfterBackup.bat. You need to manually create the AfterBackup.bat file and place it in <ConfigMgrInstallationFolder>\Inboxes\Smsbkup. ] If an AfterBackup.bat file exists, and is stored in the correct folder, the file automatically runs after the backup task is completed. The AfterBackup.bat file lets you archive the backup snapshot at the end of every backup operation, and automatically perform other post-backup tasks that are not part of the Backup Site Server maintenance task. Fellow ConfigMgr MVP Garth has published a sample AfterBackup.bat file here. Step 5. Supplemental Backup Tasks The Backup Site Server maintenance task provides a backup snapshot for the site server files and site database, but there are other items which are not backed up using this scheduled task and you must consider these items when you create your backup strategy. The following items should be backed up using whatever method you deem appropriate, for example using Data Protection Manager if that's what you use to backup data in your organization. Custom Reporting Services Reports (backup the report server database files) Content Files (Verify that you include both the content library and package source locations in your file system backup for the site server.) Custom Software Updates (backup your SCUP 11 database) In a later post I’ll show you how to restore a site backup in the event of a site failure. cheers niall Recommended reading: Restoring Backups - https://blogs.technet.microsoft.com/canitpro/2013/10/30/step-by-step-testing-system-center-2012-configuration-manager-backups-for-restoration/ Backup and Recovery in Configuration Manager - http://technet.microsoft.com/en-us/library/gg712697.aspx#BKMK_SiteBackup Support Tip: A Backup Site Server maintenance task may fail to run in ConfigMgr 2012 - http://blogs.technet.com/b/configurationmgr/archive/2012/08/01/support-tip-a-backup-site-server-maintenance-task-may-fail-to-run-in-configmgr-2012.aspx How to recover a Configuration Manager 2012 site using a restored database - http://stevethompsonmvp.wordpress.com/2014/08/01/how-to-recover-a-configmgr-2012-site-using-a-restored-db/ SQL Server backup recommendations for Configuration Manager - http://stevethompsonmvp.wordpress.com/2013/06/07/sql-server-backup-recommendations-for-configuration-manager/

the one thing you havent listed above is usb media, if PXE is failing for whatever reason you can always use standalone media

well what errors are you seeing ? is the device X86 or X64 ?

i'll post a guide about this soon (time willing) but in the meantime make sure you've got a backup of your database before starting and do a testdbupgrade on a copy of the database.

you need to find out what that package is (GR2000004) and update it to your distribution points

it should work with greater than 4gb, the keys i used in the above were 8gb in size

hi and thanks ! see my response below for details http://www.windows-noob.com/forums/index.php?/topic/6382-cannot-select-operating-system-installer/

what info did you enter on the Database Information page.

this is not a bug its a design change, when I wrote the initial guide RTM was released and SP1 was far from beta, in RTM you can select an operating system installer, in SP1 you cannot in the wizard but you can edit the task sequence afterwards to point to the intsaller if thats the way you want to do it, in SP1 the recommended way is to use the install.wim file either from a previously captured image or from the Installation media itself, this is the major design change in SP1.

then you are running an unsupported version, if you have any issues that require you to call Microsoft, Microsoft may not help you.

and how did you install it ? did you follow this guide ?

its on the CM server in the logs folder

SQL 2012 SP1 is not yet supported, see this post for details

no, currently as of today 29/1/2013 it only supports SQL Server 2012 currently (not sp1) see this post for details

hi all, i've been closely watching the growing number of views on both the Configuration Manager 2007 and Configuration Manager 2012 index of guides here, and now they've passed the 1 million mark today. I setup those index's to help people find content I created on windows-noob.com, the index's themselves just grew and grew both in content and popularity and today they finally got past 1 million combined page views. 1000343 page views ! Note: This is the number of times that those two posts have been viewed in total, it doesn't give us the total number of times all the Configuration Manager guides themselves have been viewed. You are more than welcome to click on the index's themselves to see how many times each guide has been viewed. here's some of the stats: The System Center 2007 Configuration Manager Guides http://www.windows-noob.com/forums/index.php?/topic/1064-sccm-2007-guides/ 756,048 views as of January 28th, 2013. The System Center 2012 Configuration Manager Guides http://www.windows-noob.com/forums/index.php?/topic/4045-sccm-2012-guides/ 244,295 views as of January 28th, 2013. well I think that's pretty cool indeed, and here's to the next 1 million views ! cheers niall.

no i just want to know if you took a backup of your Configuration Manager database BEFORE you attempted to ugrade ?

its under the hood and in the process, see this post for details (long story short you can now point to install.wim on the installation media instead of using Setup.exe) in fact the new build and capture process forces you this way, here's an example of that (scroll down)

did you backup your Configuration Manager database before doing this ? can you post the entire log ?

have either of the servers been rebooted recently or had any antivirus software installed or gpo changes made that could exclude the DP share from being accessed ?

have any permissions changed on that server to cause the network path to be 'not found' ?

check your client.msi.log chances are you have this issue - http://support.microsoft.com/kb/2801987

is this Configuration Manager 2012 SP1 or RTM ? did it ever work ?

ok Zach, so you are deploying a MDT 2012 update 1 captured WIM file using Configuration Manager 2012 sp1 ? can you share the unattend.xml file here with others so that they may benefit, it would of course be nice if we could do this without having to capture the image outside of Configuration Manager, if i get time i'll delve into this (if i get time...)