anyweb

ok i've moved these posts and as Peter says, please create a new topic elsewhere especially if the question has nothing to do with the original topic and as an aside, in the administration workspace, Client Settings you can suspend Bitlocker PIN Entry on restart (check the computer agent section) and you could use Compliance Settings to enforce BitLocker settings, Security Compliance Manager has many baselines connected with this that you can import and implement, look for the one called Windows 7SP1 BitLocker Security, you can then export this baseline and use it within compliance settings in Configuration Manager. that said, management of BitLocker itself is normally carried out using MBAM or via Active Directory tools

what does your smspxe.log file tell you ? search for the MAC address of the vm you are booting.

leave WDS alone, configuration manager will configure it for you. Are you using the RTM release of configuration manager 2012 ?

heh good stuff, hopefully you are only testing the CTP release in a lab as it's not for production use, cheers niall

Description of Cumulative Update 1 for System Center 2012 Configuration Manager Issues that are fixed Administrator Console When a new distribution point is added to a package that contains more than 100 existing distribution points, the new distribution point cannot be added, and you receive the following error message in the Administrator Console: The SMS Provider reported an error. When you click Details in the error message, a "Quota Violation" message is displayed that is followed by the details of the stack trace. The link to the online privacy statement for the Customer Experience Improvement Program in the Administrator Console is fixed. Application Management If a Deployment Type is added or changed before Distribution Manager processes an earlier change, the content may not be sent to a child site. The prestaged content file for a Deployment Type (DT) is not created for remote Distribution Points when there are multiple DTs for the same application. For more information about prestaged content, go to the following Microsoft TechNet website: Operations and Maintenance for Content Management in Configuration Manager Asset Intelligence Volume license editions of Microsoft SQL Server 2012 may be duplicated in the Asset Intelligence Installed_Software_data hardware inventory class. Microsoft SQL Server 2008 R2 Service Pack (SP1) is not listed in the Asset Intelligence License 01D - Microsoft License Ledger Products on a Specific Computer report. The pre-provisioned Asset Intelligence Synchronization Point certificate is updated with a new expiration date. Client When a dynamic list is used for the Install Application task sequence, not all deployment types will be installed. This issue occurs when one of the deployment types restarts the computer. In this case, any deployment type after the restart is not installed. The state messages that are associated with each application indicate Success. This issue can be seen most clearly in the smsts.log file on the client when the log file is filtered in the CMTrace for entries that contain the text "Installing application." The following is an example sequence: Installing application 'App 1' Installing application 'ContentID for App 1' has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID1}' Installing application 'App 2' Installing application 'ContentID for App 2' has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID2}' Installing application 'App 3 - Exit Code 3010' Installing application 'ContentID for App 3' has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID3}' Installing application 'App 4' Installing application 'ContentID for App 2' has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID4}' Note Both 'App 2' and 'App 4' share the same content ID. In this example sequence, 'App 4' was not installed following the restart that 'App 3' triggered. Out of Band Management Power Control and Clear Audit Log collection-based actions fail for externally provisioned AMT clients. The amptopmgr.log file contains entries that resemble the following entry: Error: CSMSAMTDiscoveryTask::Execute, discovery to client_computer failed. General Worker Thread Pool: Error, Can not execute the task successfully. Remove it from task list. Site Database Replication Link Analyzer incorrectly detects a syscommittab system table issue and suggests reinitialization if the SQL Errorlog contains the following string: 3999 A primary device cannot be selected for user-based pre-deployment if the device does not have the Configuration Manager client installed. Site Systems A Reporting Services Point may not be installed or start if the SQL Reporting Service does not start within one minute. The srssp.log file may contain entries that resemble the following entry: Starting service 'ReportServer' Time out has expired and the operation has not been completed. The SMS Executive service may stop unexpectedly if the Exchange Connector PowerShell cmdlet fails. The EasDisc.log file may contain entries that resemble the following entry: ERROR: [MANAGED] Cmdlet failed: Starting a command on remote server failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic. The Site System Status Summarizer component may cause the SMS Executive service to stop unexpectedly if the site server fully qualified domain name (FQDN) is more than 50 characters, and the default installation path is used. The relevant entries from the Exception Information section of the crash.log files contain the following entry: Thread name = SMS_SITE_SYSTEM_STATUS_SUMMARIZER Executable = C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe Exception = eeeeffff (EXCEPTION_SMS_FATAL_ERROR) Known issues Update of the Administrator Console When the Administrator Console is first installed, a copy of the Adminconsole.msi file is cached in the %Temp% folder of the user who initiated the installation. If that MSI file is missing, the Configmgr2012adminui-rtm-kb2717295-i386.msp update file may not be applied. When this update is distributed by using Software Distribution, the installation may fail, and an exit code of 1603 is logged in the excecmgr.log file. To resolve this issue, reinstall the original release of the Administrator Console by using Consolesetup.exe, then apply this update. Back to the top | Give Feedback How to obtain Cumulative Update 1 for System Center 2012 Configuration Manager A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. Back to the top | Give Feedback File information The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. Download it here

Data error (cyclic redundancy check). < run chkdsk on the drive you are trying to capture from, oh and please tell me you are not building an image on real hardware ? and then capturing it ? that will cause you problems and makes it harder to automate everything if at all possible, try to build and capture on virtual hardware and use a separate task sequence to deploy the captured image to multiple types of hardware

hi Julian zip up all the logs on that client in it's CCM\LOGS folder and attach them here, if you cannot attach them then use skydrive or dropbox.

add a Restart Computer step after it has captured User state as in the screenshot below then you'll be ok, review the following to see why http://support.micro....com/kb/2018585

can you attach your unattend.xml please ? and both smsts*.log files

use ADR (automatic deployment rules) to do your patch tuesday monthly updates. I'll do a new post on that sooner or later

hi SpecialEd, the reason I've chosen to use custom ports is because it's a recommended best practice from Microsoft, see here as regards your original issue, do you have any of the logs you sent to Microsoft i'd be happy to look at them to figure out your problem

where is it failing, scanstate (backup) or loadstate (restore) the following logs will help you find out smsts.log scanstate.log loadstate.log

As promised, Microsoft today released the final version of Windows 8 to MSDN and TechNet subscribers. But it also posted a 90-day evaluation copy of Windows 8 RTM (release to manufacturing) that anyone can download. At approximately 1 p.m. ET, members of TechNet began reporting that Windows 8 RTM was available. "Downloading Windows 8 Enterprise now, with an Enterprise Multiple Activation key," said Ken Schannen, in a message posted on the TechNet discussion thread. "I also see Windows 8 Pro with 3 keys available." Others chimed in that they had start downloading, too. Not surprisingly, some subscribers said Microsoft's servers were sluggish under the strain. "TechNet is dying under the stress of all the downloads," said someone identified only as "Mercutio84" on a different thread. The MSDN (Microsoft Developer Network) download site listed all versions of Windows 8 RTM (release to manufacturing), including Windows 8, and Windows Enterprise. The last targets businesses that have volume licensing plans in place. Two weeks ago, Microsoft announced that Windows 8 had reached the RTM milestone, and would be available to MSDN and TechNet subscribers today, Aug. 15. Companies with Software Assurance licensing agreements and members of the Microsoft Partner Network will be able to grab Windows 8 starting tomorrow, Year-long TechNet subscriptions start at $199, while the least-expensive MSDN subscription -- which lets members access only operating systems -- costs $699. But Microsoft has also made available the Enterprise edition of Windows 8 RTM to anyone willing to invest some download time. Although the company said the 90-day trial copy was "intended for developers building Windows 8 apps and IT professionals interested in trying Windows 8 Enterprise on behalf of their organization," those who don't fit into those two categories -- enthusiasts eager to get their hands on the finalized code, say -- aren't blocked from downloading the eval edition. Computerworld was able to register for the trial and begin the download process of Windows 8 Enterprise RTM without incident. The download generates an .iso file, or disk image, that must be burned to physical media, such as a DVD or a flash drive, or installed in a virtual machine. Unlike the versions distributed via TechNet and MSDN to paying subscribers, the evaluation expires after 90 days of use. At that time, Windows 8 blackens the desktop background, displays a persistent notice that the OS is not genuine, and most draconian of all, shuts down the PC every hour without giving the user a chance to save works in progress. When the evaluation period expires, users will have to replace it with a purchased copy or another operating system, and reinstall all applications, other software and files. "It is not possible to upgrade the evaluation to a licensed working version of Windows 8," Microsoft warned. If a user downloads and launches the evaluation copy today, it will run until Nov. 12, 2012, about two-and-a-half weeks after Microsoft officially launches Windows 8. The trial copy of Windows 8 Enterprise must be activated within 10 days of its first launch, but Microsoft said a product key was not required. It is available in Chinese, English, French, German, Italian, Japanese, Korean, Portuguese and Spanish. To download the 90-day try-before-you-buy -- available in 32- and 64-bit versions -- start at this Microsoft website. The 32-bit trial tips the bit scales at 2.4GB. via ComputerWorld > http://www.computerworld.com/s/article/9230317/Microsoft_offers_free_Windows_8_RTM_eval_to_everyone

make sure to look at this too :-) Introducing the BitLocker FrontEnd HTA Multipurpose HTA with BitLocker Support for all three common scenarios, backup, reinstall, new computer [added Jan 2012]

the 32 bit boot image can be used to deploy both X86 and X64 images,

nope, changes to the task sequence steps don't require you to distribute content, unless of course you add a step that references content that has not already been distributed, or which has changed since being distributed

I dont see a way of doing it using the AntiMalware policy but perhaps you could query for this state and using a script force the reboot (ie: a package/program) based on collection membership.

it's not supported yet but it looks like support (for server 2012) is coming in Service Pack 1 see here

did you apply the command support change to both architecture boot images ? we really need your smsts.logs to help

yes you can, are you planning on using a SMP (state migration point) ?

your question is a bit confusing but if you want to break up the processes you can, simply create more than one task sequence to do so.

well you'd want a zero touch solution with mandatory advertisements, which can be very risky if done incorrectly, or add some interaction and make the advertisements optional

interesting and thanks for posting, i've added a troubleshooting note to that guide now to clearly show how to know if it's working correctly (or not) by reviewing the WUAHandler.log, I think you may have specified the Netbios name instead of FQDN (if your site server was configured that way), please review the troubleshooting note and see does it correspond to your logs, and yes, you can absolutely specify this GPO for installing clients using the SUP and it does not adversely affect Endpoint Protection or other updates later on, you can see this by reviewing part 6 which uses the SUP (with the configured GPO) to install Endpoint Protection Definition Updates.

hold on a minute, where are the task sequences advertised to ? which collections ? the unknown computers collection ? or just 'deploy' collections ? describe the process you go through to get a 'new' computer imaged (are you importing its name/mac into ConfigMgr ?) secondly, what does the component status of your server look like, is it complaining about anything in particular, like your management point ?

can you attach an smsts.log from one of these deployments please ? i doubt the installation of that update would break your osd and stop them at boot time, something else is wrong