Jump to content


anyweb

Root Admin
  • Posts

    9245
  • Joined

  • Last visited

  • Days Won

    368

Everything posted by anyweb

  1. there is no option to restore the backed up WIM in the CM12 BitLocker Frontend HTA, all restore options are for data backed up via scanstate, I may add a restore wim option in a later addition (actually i'm working on a backup/restore HTA separately which is dedicated to network backup, you'll need to restore the wim file and the corresponding bootloader. like so.... (here are some of the steps I use, each one is a separate step) I may release a version of this functionality in the future but right now it's being developed.. Set %OSdisk% = C: if OSDISK doesn't exist x:\windows\pkgmgr\imagex.exe /apply %RESTORE_FILE% 1 %OSDISK%\ /logfile x:\windows\pkgmgr\imagex.log cmd.exe /c bootsect.exe /nt60 %OSDISK% /force /mbr cmd.exe /c bcdboot %OSDISK%\Windows
  2. Today, June 10, is Microsoft Patch Tuesday. It's also the deadline for consumers running Windows 8.1 to install the Windows 8.1 Update if they want to continue to receive patches and fixes from Microsoft. Microsoft originally imposed a deadline of May 13 on consumer users to move to the Windows 8.1 Update. On May 12, Microsoft announced a deadline extension to June 10. Business users still have until August 12 to move to the Update for Windows 8.1 and Windows Server 2012 R2. Microsoft extended the deadline for those updating using Windows Server Update Services (WSUS), Windows Intune, and/or System Center Configuration to update users' machines. Microsoft execs unveiled the new deadline in mid-April after outcry from some that Microsoft wasn't giving them enough lead-time to apply the update. Consumers running Windows 8.1 who have Automatic Updates turned on don't need to do anything; they should have received the Update automatically via Windows Update by now. Users who are on Windows 8, not Windows 8.1, are not subject to the requirement to move to Windows 8.1 Update by June 10. (Microsoft has set January 2016 as the end support date for Windows 8 users who haven't moved to 8.1.) Those running Windows 8 who are interested in moving to Windows 8.1 Update do not need to move to Windows 8.1 first, as these updates are cumulative. The Update for Windows 8.1 included a number of new features designed to make Windows 8.1 more easily navigable by those using keyboards and mice. via ZDnet > http://www.zdnet.com/windows-8-1-consumers-its-time-to-move-to-update-1-7000030378/
  3. I'd appreciate if you create a new thread describing your issues, as this thread is all dedicated to the CM12 BitLocker FrontEnd HTA. then once done we'll deal with your issues, one at a time
  4. if you create an mdt boot image then that should support this task sequence, have you tried that ? or create a boot image with optional components installed which can support displaying HTA's
  5. i'll retest, i was setting ospart, i'll set osdisk with the ospart var...
  6. interesting, when I set that variable it made no difference (was setting it with the checkdriveletter script), however it works fine for me using MDT 2013, and I also use a variable called BackupDrive by setting BackupDrive=All which backs up all partitions (except bde partitions) I have not tested it with recovery partitions yet
  7. what does the installation log for Office tell you ? attach it here if you can
  8. no i dont, and i didn't get time to update my lab tonite either, i'll try tomorrow.
  9. no need to recreate the ts, simple change your Use Toolkit packages steps from MDT 2012 to MDT 2013..
  10. wasn't this linked to in the actual post ? The CM12 BitLocker FrontEnd HTA - video what bit are you missing exactly ?
  11. oops yeah i'll upgrade my lab tonite and verify it for you, then i'll let you know,
  12. please try the latest version of MDT 2013 and tell me what result you get.
  13. which version of MDT are you using ?
  14. it's the MDT Toolkit package, created when you create your first MDT Integrated task sequence in CM12
  15. amongst the many errors (such as running the media twice and from different drives (d:,e:) I think the actual error is here can you tell us how you've prepared your client operating system ? does it have the configuration manager client installed ? if so what version >? can you try uninstalling it using the command below then reboot once done and try again ccmsetup /uninstall
  16. does the fix mentioned here work ? http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/mostViewedDisplay?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_efb5c0793523e51970c8fa22b053ce01=wsrp-navigationalState%3DdocId%253Dmmr_kc-0108200-6%257CdocLocale%253Den_US&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&sp4ts.oid=5177961&ac.admitted=1402212562009.876444892.199480143
  17. the 0x80008013 error is a return result failing to detect that the dependency was installed. E_FAIL_DEPENDENCY_NOT_RUN 0x80008013 http://technet.microsoft.com/en-us/library/bb632794.aspx what log are you generating when installing IE10 ? review it to see what dependancy you are missing...
  18. well there are a few things to check, have any software updates been deployed to your clients ? are the Configuration Manager client agents working on your clients ? are the folders you showed above populated with updates ? what do your logs tell you on your Configuration Manager server...
  19. Microsoft won't be delivering a new Start Menu for Windows 8 with its coming Windows 8.1 Update 2, after all. That recent change in plans comes courtesy of a couple of my sources who've had good track records on Windows information. Up until recently, Microsoft was hoping to make a new "Mini" Start Menu part of a second update to Windows 8.1. Windows 8.1 Update 2 was -- and still is, last I heard -- slated to arrive in August of this year. Microsoft's operating systems group has decided to hold off on delivering a Microsoft-developed Start Menu until Threshold, the next "major" release of Windows. Threshold, which may or may not ultimately be called Windows 9, is expected to be released in April 2015. I'm not clear whether the postponement is because the feature won't be fully baked in time, or if there's another reason for the change in plans. Microsoft still is moving full steam ahead with plans to try to make Windows 8.x more palatable and usable by those using mice and keyboards, as well as those used to previous Windows iterations. That strategy hasn't changed. The new Microsoft-developed Start Menu isn't going to be the same as the Windows XP/Vista/Windows 7 Start Menus; it's expected to offer some familiarity, but also integrate Windows 8's Metro-Style Start screen concept. (For those who prefer the more traditional Windows Start Menu experience, there are a few third-party-developed Start Menus for Windows 8 on the market including Start8 from Stardock and the Pokki Windows 8 Start Menu.) Terry Myerson, the Microsoft Executive Vice President who runs the unified operating system group, showed off a Start Menu mock-up during Microsoft's Build conference in early April, noting that Microsoft was going to bring a Start Menu back to Windows as part of the "next iteration" of the operating system. He didn't specify whether that meant Windows 8.1 Update 2 or Threshold, but based on leaks later in April, the internal plan was to make the Start Menu part of Update 2. Myerson also showed off in early April a new option to run Metro-Style/Windows Store apps to run in windows on the Desktop. I'm still hearing that windowed Metro-Style apps functionality remains a Threshold deliverable, not a Windows 8.1 Update 2 deliverable. So now what's going to be in Windows 8.1 Update 2? Will there be any user-interface changes or will it be more a vehicle for under-the-covers programming interface and reliability improvements? I don't know at this point. via Zdnet > http://www.zdnet.com/no-microsoft-start-menu-for-windows-8-until-2015-sources-7000030100/
  20. you could use standalone media (usb or cd/dvd)
  21. can you attach your smsts.log please so i can take a look
  22. well you can prove that nic drivers are needed by opening a command prompt during OSD just before the setup windows and configmgr step, does it have an ip address, if so good, what about after the reboot after setup windows and configmgr, if it has no ip at this point then there's your problem as it's then that it tries to join the domain. why not use hyperV. no network drivers are needed at all for hyperV and it's free with Windows 8, Windows 8.1
  23. it's no problem, you can always decide which index of the captured image (1 or 2) you wish to apply in the Apply Operating System step.
  24. did you deploy both task sequences ?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.