anyweb

please explain what those errors were so that the next person searching on the same topic knows what to look out for

correct, also to note the mbam client can store the key in AD also

in packages choose Create Package From Definition and select your client package listed in the window *choose the latest option from the list*, select always obtain source files from ...and then select Network Path (UNC name) as the type and click on browse, browse to your sites SMS directory (SMS_xxx where XXX=the SMS site code) eg: \\server\sms_XXX\Client continue through the wizard choosing 'no program', once done, distribute to your distribution points, and use that client package in your task sequences, is that enough info ?

are the clients confirmed working and in the collection where the software updates are targeted to ?

There's nothing like ending the week with a few fresh Windows rumors.First up, the target release date for Windows 8.1 Update 1 -- the relatively minor update coming to Windows 8.1 this spring -- is allegedly March 11, according to one of my accurate and trusted sources. Yes, that's a Patch Tuesday. Given that Microsoft will likely deliver Update 1 to Windows 8.1 users via Windows Update, this seems pretty believable to me. Windows leaker WZor previously indicated that Windows 8.1 Update 1 would likely be released to manufacturing in March, but didn't provide a specific date. One more tidbit about Windows 8.1 Update 1 from my aforementioned source: Update 1 may feature some of the work that Microsoft has been doing behind the scenes to reduce further the memory and disk space requirements for Windows. This would allow Windows 8.1 Update 1 to run on cheaper small tablets. Windows 8.1 Update 1, screen shots of which leaked earlier this week, is expected to allow users to pin Metro-style/Windows Store apps to their desktop task bars. Thumbnail previews of these Metro-style apps will be available from the Desktop task bar, according to additional screen shots. Windows 8.1 Update 1 also is expected to include close boxes for Metro-style apps. If Microsoft does hit the March 11 date with Windows 8.1 Update 1, that release will hit just a few weeks before the Windows Phone 8.1 operating system supposedly will. Rumors have indicated that Windows Phone 8.1 (a k a "Blue") will RTM just prior to the kick off of Microsoft's Build 2014 conference, which starts April 2. From what I've heard, Windows Phone 8.1 won't be available to consumers until later this April, at the earliest, though developers will likely have access to the bits sooner than that. Even though the arrival dates for Windows 8.1 Update 1 and Windows Phone 8.1 are relatively close, it's now sounding from my sources that there won't be application programming interface (API) changes made to Windows 8.1 Update 1 to bring it into closer alignment with Windows Phone 8.1. Instead, Windows 8.1 Update 1 will be focused primarily on making Windows 8.1 more useful to business users. read the full story at ZDnet > http://www.zdnet.com/microsofts-windows-8-1-update-1-rumored-release-target-is-march-11-7000025559/

yes you can store the keys in mbam (an SQL database) and AD at the same time, when enabling bitlocker in the task sequence using the built in step you can choose to store the key in AD, then later in the task sequence you install the mbam client and it stores the key in it's database, as it can take up to 90 minutes (unless you add the nostartupdelay reg key) for MBAM to store its key in the db, having a backup copy in AD is a good idea.

correct, assuming of course that the Configuration Manager site server has appropriate permissions to write to the System Management container in AD

great stuff and i'm glad you've got it all sorted now

what version of Configuration Manager and CU level are you at and how long have you tried waiting ?

check what its copying is it copying every package on your share ?

here's proof it failed it seems that after setup windows and configmgr it reboots but fails to continue can you verify what steps are in your task sequence and does the client get installed at all (c:\windows\ccmsetup\ccmsetup.log)

post your smsts.log(s) here and we'll take a look the screenshots of them isn't enough info - look in c:\windows\ccm\logs after the deployment is done and post all the SMSTS*.log files here

after you added the driver to the boot image did you update it to the dp's and did you verify that the boot image you are using is the one attached to your task sequence

i presume you are trying to create an MDT boot image from within Configuration Manager ? what vesion of configuration Manager is it and what version of MDT have you installed ? the problem you have is actually a bug, see the solution here.

where are you running your steps, before or after setup windows and configmgr (hint, try after)

from your logs... I can see it's filling up your D:\ drive (possibly your WinPE) so check what drive you are deploying to, I have a task sequence script in the sample task sequence here which checks what drive is the OS drive by looking for \windows\explorer.exe and sets that variable for use later... if your computer has multiple partitions and you've pointed it to the wrong partition then it will bomb out... to make troubleshooting this easier i'd definetly advise you to implement the following in your task sequence so you can step through it http://www.windows-noob.com/forums/index.php?/topic/8846-how-can-i-pause-a-task-sequence-in-system-center-2012-configuration-manager/

more information about setting up a KMS server and other questions here http://www.windows-noob.com/forums/index.php?/forum/88-kms/

if your cm07 environment has mdt steps in the task sequences, then remove those steps first (it won't migrate the task sequence otherwise) then migrate the task sequence (minus the MDT steps) using CM migration task, then add-back the missing MDT steps with your chosen version of MDT integrated with CM12.

I thought i had added that info to the guide but i guess i didn't, i've added it now, and by the way, it's unsupported to created media (iso for cd/dvd) and then copy/extract to USB, it may work, but it unsupported, if you want to create usb media in a supported way, then use the wizard for USB creation.

ADK 8.1 is required for System Center 2012 R2 Configuration Manager as described in this post.

At the BUILD developer conference in April 2014, Microsoft will discuss its vision for the future of Windows, including a year-off release codenamed "Threshold" that will most likely be called Windows 9. Here's what I know about the next major release of Windows. As a kind of recap, we know that Microsoft will update Windows 8.1 in 2014, first with a service pack/feature pack-type update called Update 1 (or GDR1 internally). I wrote a bit about this update recently in Windows 8.1 Update 1 (Very Early) Preview but the expectation is that it will ship in April 2014 alongside Windows Phone 8.1, the development of which Microsoft will soon complete. Also in April, of course, is BUILD 2014. That show will hit just weeks after Microsoft completes its corporate reorganization and will surprisingly be very much focused on Windows Phone and Xbox, according to my sources. But I think Windows watchers will agree that the biggest news from the show will be an announcement about Microsoft's plans for the next major Windows version, codenamed "Threshold." I previously wrote about Threshold in Microsoft to Take Windows to the "Threshold", Further Changes Coming in Windows "Threshold" and Big Changes Are Coming to Windows. This is the release my sources previously pegged as being the one that will see the return of the Start menu and the ability to run Metro-style apps on the desktop alongside desktop applications. But Threshold is more important than any specific updates. Windows 8 is tanking harder than Microsoft is comfortable discussing in public, and the latest release, Windows 8.1, which is a substantial and free upgrade with major improvements over the original release, is in use on less than 25 million PCs at the moment. That's a disaster, and Threshold needs to strike a better balance between meeting the needs of over a billion traditional PC users while enticing users to adopt this new Windows on new types of personal computing devices. In short, it needs to be everything that Windows 8 is not. Here's what I've learned about Threshold. Windows 9. To distance itself from the Windows 8 debacle, Microsoft is currently planning to drop the Windows 8 name and brand this next release as Windows 9. That could change, but that's the current thinking. BUILD vision announcement. In case it's not obvious that the Sinofsky era is over, Microsoft will use BUILD to provide its first major "vision" announcement for Windows since, yes, Longhorn in 2003. Don't expect anything that grandiose, but the Windows team believes it needs to hit a happy middle ground between the KGB-style secrecy of the Sinofsky camp and the freewheeling "we can do it all" days that preceded that. As important, the firm understands that customers need something to be excited about. No bits at BUILD. Microsoft will not be providing developers with an early alpha release of "Threshold" at BUILD, and for a good reason: The product won't even begin development until later that month. Right now, Microsoft is firming up which features it intends to deliver in this release. Metro 2.0. Maturing and fixing the "Metro" design language used by Windows will be a major focus area of Threshold. It's not clear what changes are coming, but it's safe to assume that a windowed mode that works on the desktop is part of that. Three milestones. Microsoft expects to deliver three milestone releases of "Threshold" before its final release. It's unclear what these releases will be called (Beta, Release Candidate, etc.) or which if any will be provided to the public. April 2015 release. Microsoft is currently targeting April 2015 for the release of Windows 9 "Threshold." more via WinSuperSite.com > http://winsupersite.com/windows-8/threshold-be-called-windows-9-ship-april-2015

due to popular demand with the following download i'm including all the bugfixes mentioned above in the downloadable code below, note that this task sequence was also exported from System Center 2012 R2 Configuration Manager so it works just fine with R2. The CM12 BitLocker FrontEnd HTA.zip

yes if the task sequence completes successfully it should be removed by the process, so this tells me that your task sequence is not completing successfully, look at the smsts.log file and determine what is going wrong

you came to the right place, the best way to troubleshoot it is via the logs use CMTRACE.exe to view the logs as the problems will show themselves much easier feel free to post the logs here and we can take a look.

post your logs here so we can see the real error. if it doesn't know what the %systemdrive% variable is it will fail.