anyweb

are you sure no other window is waiting on your input, have you closed and re-opened the console ?

you need to grab the smsts.log from the failed pxe boot before the C0000001 message above appears (and after pressing f12), so have you tried that ?

are you attempting to edit task sequences on the server itself (with the server console) or via a remote console ? has anyone changed any of your permissions ? can you create a new custom task sequence, does that work ?

if you are having hardlink issues then please raise a new topic outlining your problems, to include a log file simply click on the 'more reply options' in the bottom left corner of the post.

if you are using a mix of devices then what boot images are deployed in your task sequences ? if they are all x64 bit boot images then all is fine, if they are x86 and x64 then the last task sequence deployed to your osd collection will be the one that 'wins' - it follows the LIFO statement (last in first out) what error messages are you seeing exactly ?

Few golden geese in technology have survived as long as Office has for Microsoft. The suite of applications that includes Word, Excel and PowerPoint, first released in 1990, generated nearly a third of Microsoft's revenue during its last fiscal year — about $26 billion of $87 billion in total. By some estimates, the software accounted for an even higher portion of the company's gross profits. But in a sign of the seismic changes underway in the tech industry, Microsoft, the world's largest software company, said on Thursday that it would give away a comprehensive mobile edition of Office. The free software for iPads, iPhones and Android tablets will do most of the most essential things people normally do with the computer versions of the product. Just a few years ago, giving away a full free version of Office would have earned a Microsoft chief executive a visit from a witch doctor. Now, the move is following through on the rallying cry coming from Satya Nadella, Microsoft's new chief executive, who has pushed cloud and mobile computing as lodestars for the company's future. The old Microsoft hemmed and hawed about creating Office apps for mobile platforms from Google and Apple, pushing its Windows platform instead. But the center of gravity in the tech industry has quickly shifted to mobile and cloud computing. Power players like Apple and Google and many of the most successful new start-ups now offer free software, often with premium perks for sale. read more > http://www.cnbc.com/id/102159969#.

hi Chris sure thing, just use the guid/uuid or use this method http://blogs.technet.com/b/askpfeplat/archive/2014/07/28/how-to-use-the-same-external-ethernet-adapter-for-multiple-sccm-osd.aspx

are you running this on the Surface Pro 3 or some other model, the guide was specifically for the Surface Pro 3, hence that WMI query.

no need to extend the schema again, it's a one time operation,

Does the Surface Pro 3 still have the original factory installed image on it ? have you tried network booting it using a Microsoft USB network card, does that work or not ? do any of your devices succeed in UEFI network booting (as this requires UEFI network boot, not PXE/legacy boot...) you say you've updated to the latest firmware, how did you do that cheers niall

could be a lack of space in your temp drive, check your environmental variables to see where temp is by typing set

without further details i'm guessing you are missing network drivers can you post the SMSTS.log file from a failing machine please ?

1. yes 2. yes cheers niall

you need to set the value for the default user account before any user logs on, that way all new user accounts created have the desired value, like so..where %OSDISK% is the drive with windows on... you can either create a script or run as a run command line step at the end of the task sequence reg load HKU\Default %OSDisk%\Users\Default\ntuser.dat reg add HKU\Default\Software\Microsoft\Windows\CurrentVersion\Explorer\StartPage /v OpenAtLogon /t REG_DWORD /d 1 /f reg unload HKU\Default or via group policy, Boot to Desktop using Group Policy Open Group Policy Management Console Right-Click on your Windows 8.1 Users Group Policy and select "Edit" Navigate to the following section: User Configuration\Administrative Templates\Start Menu and Taskbar Locate the following setting: "Go to the desktop instead of Start when signing in or when all the apps on a screen are closed" (yes – it’s really called that) Enable the setting

if you are sure that your setup is all ok, then i would advise you to place a support call with Microsoft Intune, see what they say.

For those of you that are not aware, there's a Deployment Roadshow coming in December by three of the greatest OSD Guru's on the planet, Johan Arwidmark, Mikael Nystrom and Michael Niehaus. The event details are below, these guys really know there stuff and are a joy to watch/listen, sign up if you get the chance ! Windows 10 & Windows Server Technical Preview Suddenly it happens! Windows 10 and Windows Server Technical Preview has been released as early test versions and it’s time to get your teeth into everything new before it is released. Therefore, we have invited over legend and one of the world’s premier on Windows and OS Deployment – Michael Niehaus, the man who created the MDT. Together with Mikael Nyström and Johan Arwidmark, he delivers a day filled with news about the new Windows Client and Windows Server. Knowledge Factory and TrueSec arranges Deployment Roadshow, a technical seminar on the deployment and management of Windows 10 and Windows Server Technical Preview. As usual it is a demo intensive day, based on accumulated experience from the TAP program. And the fact that we have actually been using this new platform in production. We will visit five locations in Sweden and Norway, between the 1st and 5th December 2014. More information and registration. The event details in Swedish here > http://events.truesec.se/Event/Deployment_Roadshow cheers niall.

not supported as you can imagine, however why not just deploy the image from MDT and install the intune client that way ? or as a longshot use the smstspostaction variable to run a script which uninstalls the ccm client and then installs the intune client.

did you try pressing left shift and f10 ?

hi the following guides will help you get MDT working with Configuration Manager if you follow them step by step CM12 in a lab - Part 16. Integrating MDT 2012 RC1 with Configuration Manager 2012 CM12 in a lab - Part 17. Using MDT 2012 RC1 with Configuration Manager 2012 CM12 in a lab - Part 18. Deploying a UDI Client Task Sequence once done, if you want to setup a clean MDT environment for building images then you could use this script to create a standalone environment from scratch and just modify the variables to suit your setup as regards capturing your master image, either do it in MDT or use capture media in Configuration Manager to capture the wim file, or use a pxe based build and capture task sequence, some links below. CM12 in a lab - How can I capture an image using Capture Media in Configuration Manager 2012 ? CM12 in a lab - Part 7. Build and Capture Windows 7 X64 using System Center 2012 Configuration Manager - Part 7. Build and Capture Windows 7 X64 SP1

here's another take on that CM12 in a Lab - How can I dynamically deploy multiple operating systems with System Center 2012 R2 Configuration Manager ?

Introduction In a previous post I showed you how you can deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using System Center 2012 R2 Configuration Manager. The Surface Pro 3 comes with a re-worked pen that has bluetooth capability and some additional functionality to do some very cool things. When you get a Surface Pro 3 directly from the store and start it up, you'll go through a process called Out Of Box Experience (OOBE) and this process will gather some information from you in addition to allowing you to pair the bluetooth pen with your new Surface. I wanted to add that functionality back when deploying the Surface but you need a few things in place before you can do it, and once you do have the ability, you cannot control it that much (you'll see what I mean later in the video). But before I start take note of the note below. Note: This process will only work when you use Windows 8.1 x64 Update, in other words the media used must be the 'update' to Windows 8.1, if you try this on regular Windows 8.1 then nothing will happen. Step 1. Download the files Get the four files from a brand new Surface Pro 3 (one that has not been reimaged) in the following folder C:\Windows\System32\oobe\info\default\1033. If you don't have access to those files you can download them from here. oobe.zip Unzip the attachment and copy the files to your Configuration Manager server (for example copy them to \\sccm\sources\os\Tools\oobe) Step 2. Create a new package Create a new package by right clicking on Packages in Software Library as shown below give the package a suitable name like Surface Pro 3 Pen Support as shown below do not create any program as none is needed complete the wizard Step 3. Distribute the package to your distribution points Locate the package, and right click, choose Distribute Content as shown below click on Add, then select distribution point choose from your available distribution points and click on ok and then next when done the Distribute Content wizard is complete Step 4. Add a Run Command Line step to your task sequence Edit your previously created Deploy Windows 8.1 to the Microsoft Surface Pro 3 task sequence and add a run command line step, the step must occur before the Setup Windows and Configuration Manager step and after the Apply Operating System step Paste the following code into the step, note that it's looking in a folder called OOBE in your package. xcopy ".\OOBE\*.*" "C:\Windows\System32\oobe\info\default\1033" /D /E /C /I /Q /H /R /Y /S next select the package we created above as shown below, click apply when done finally, click on the Options tab and select WMI Query from the drop down options, paste in the following code SELECT * FROM Win32_ComputerSystem WHERE Model Like "%Surface Pro 3%" as shown below Step 5. Deploy a Surface Pro 3 and observe the new behaviour In the video below I show you exactly what you should see when the above steps are done, note that this will not show up on a virtual machine as the step is set to only run if a Surface Pro 3. And that's it, job done If you do not succeed in pairing the pen during Windows setup, you can do it after the event, while in Windows by clicking on Settings and configuring your bluetooth devices (pairing). until next time, adios ! Related Reading CM12 in a Lab - Why is my Surface Pro 3 not BitLockered after OSD via System Center 2012 R2 Configuration Manager ? CM12 in a Lab - Where do I find the MAC address of my Surface Pro 3 Ethernet Adapter in order to use UEFI network boot ? CM12 in a Lab - How can I deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using System Center 2012 R2 Configuration Manager ? CM12 in a Lab - Why does my Surface Pro 3 take a very long time to UEFI Network Boot using System Center 2012 R2 Configuration Manager ? CM12 in a Lab - How can I sync the BIOS date in WinPE to avoid PXE boot failure with System Center 2012 R2 Configuration Manager ? MDT 2013 - How can I deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using MDT 2013 ? Summary Adding Pen Support to the Surface Pro 3 during the OSD process using System Center 2012 R2 Configuration Manager is easy once you know how, just remember to use Windows 8.1 X64 Update as the version of Windows, otherwise it will fail to run the OOBE process.

got a valid ip adress in winpe ?

There's a new build available (build 9860), and you can get it like so, click on the start icon, type in Windows Update Settings as shown below when Windows Update Settings opens up, select Preview Builds and then select Download now after it's downloaded you'll be prompted to install it, and after a short installation, you'll be prompted to restart, you can choose restart Now or delay it for up to 8 hours via the drop down menu for more info about what's new in Build 9860 see below from ZDnet http://www.zdnet.com/whats-in-the-latest-windows-10-technical-preview-update-build-9860-7000034929/

assuming you've completed my guide above and have run the script, and everything finished successfully, then try expanding Advanced, select Media, right click and choose New Media point to a blank folder (such as E:\Media) for the Media Path step and select the Everything selection profile as shown below continue through that wizard until completion, here's the powershell to do the above Import-Module "C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1" New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\DeploymentShare" new-item -path "DS001:\Media" -enable "True" -Name "MEDIA001" -Comments "creating bootable media for the Surface Pro 3 (c) windows-noob.com October 2014" -Root "E:\Media" -SelectionProfile "Everything" -SupportX86 "True" -SupportX64 "True" -GenerateISO "True" -ISOName "LiteTouchMedia.iso" -Verbose new-PSDrive -Name "MEDIA001" -PSProvider "MDTProvider" -Root "E:\Media\Content\Deploy" -Description "Embedded media deployment share" -Force -Verbose Next, manually copy BootStrap.ini and CustomSettings.ini from E:\DeploymentShare\Control to E:\Media\Content\Deploy\Control and answer yes to the replace. Next, right click on the new Media, choose properties remove support for the X86 boot wim as it's not needed for support Surface Pro 3 Select the Windows PE Tab, and choose the drop down for X64, then select Drivers and patches and make sure the WinPEx64 selection profile is selected close the wizard when done. Finally, right click the Media001 and choose Update Media Content, continue through that wizard or use this powershell script Import-Module "C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1" New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\DeploymentShare" Update-MDTMedia -path "DS001:\Media\MEDIA001" -Verbose Once done, browse to your media folder, eg: E:\Media and use the ISO provided to image your Surface Pro 3. alternatively, you can mount the ISO and copy the contents to a FAT32 formatted usb key/disc and boot from that instead, you might need to use diskpart to make that partition (vol) active, the USB disc must be formatted as FAT32 as UEFI devices cannot boot from USB media formatted as NTFS.

thanks ! can you access that address via a web browser ? is the internet connection proxied ?