Jump to content

Search the Community

Showing results for tags 'usb'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Found 9 results

  1. Hi everyone, I am attempting to do my first UEFI-based SCCM install for Windows 10x64 for my firm. Previously, we had Windows 7x86 installed on these devices, and everything worked fine. Attached is the driver list that i am currently using in my x64 boot disk. When I try to do the bootup - I get the below message... Status: 0xc0000001 Info: A required device isn't connected or can't be accessed Any ideas? Thank you in advance.
  2. Hi All, Hope you are all well, and sccm'ing away on the CBB I have been asked to look into a standalone task sequence from usb, which will include the djoin steps for a offline domain join. I went thru the djoin provision steps etc process manually in a lab, and got a fresh build win10 box to join the domain. but cannot seem to get this to work with vanilla sccm cbb. I have read articles that mdt has a specific step for this, but I'm not sure the boss wants mdt in place ?? Anyone got experience of a way to get this to work ? Regards, Wazzie
  3. I created a Windows XP 32bit to Windows 7 64bit Migration Task and put the entire task sequence/apps/drivers on an external usb drive. The task would not run because it was detecting the external drive as a local disk. I moved the sequence/apps/drivers to a USB 2.0 disk and it worked perfectly. I purchased 2 USB 3.0 SanDisk extremes to make the migration significatly faster. After moving the sequence/apps/drivers I ran the task, it failed instantly. I found the that SanDisk in order to be Windows 8.1 “Windows to Go” complaint has turned all their new flash drives to register has “Local Disks”. Is there any way to using these or an external USB HDD as my migration media?
  4. Hi all I'm migrating a number of computers at remote sites from XP 32 to 7 64. The upgrade will be done by sending around a USB drive which will have a task sequence on it to upgrade them. As we are using SCCM 2007, I'm largely following this guide: http://www.windows-noob.com/forums/index.php?/topic/1735-using-offline-mode-in-windows-pe-using-usmt-4-via-a-task-sequence-in-sccm-2007-sp2/ My problem is that at some of the sites, the 80GB hard drives are split 40GB/40GB between C: and D: and I rather than run the risk of maxing this out mid-process, or leaving the disk near full capacity once reimaged, I'd like to use the "Partition Disk 0" Task Sequence step and get the full 80GB back. Obviously with the c: being formatted, I am unable to store my user state data there, So, my plan is to use the USB with the task sequence on it, with enough free space for the USMT to migrate the data to, as well as a few other files and registry keys. I'm not sure how to do this and my google-fu is failing me here. I'm thinking along the lines of the following... Do inserted flash drives automatically get mounted as D:? (I'd imagine not as you need to set %systemdrive% manually) I understand x: is the WinPE location - If the task sequence is on USB does this mean x: = usb? Can I somehow mount the USB drive using a task sequence? If anyone has any experience with this I'd be rather grateful! Thanks
  5. Edit: Posted this in the wrong location. Mods, feel free to delete while I look for a way to do that myself. Moved to: http://www.windows-noob.com/forums/index.php?/topic/8393-2007-offline-scanstate-to-usb-drive/
  6. Hello, I am trying to create an ISO from my offline media so that we can copy it to a central location and people can make their own bootable USB. The problem is that our complete offline image is almost 11GB and when you create a ISO through the SCCM console, it breaks the ISO up into 8.5 GB and another 2.x GB. There inst an option to leave the whole thing in tact. How can I get only one full sized ISO that others can burn without having to create a bootable USB through the Console itself or does anyone have any programs that I can convert my working offline USB into a bootable ISO? Thanks!
  7. Does anyone here use USB Task Sequence media? Assuming you have a 'reboot' step within your task sequence, and aside from modifying the boot sequence, how do you prevent the PC from rebooting and booting from the USB stick straight back into the WinPE Task Sequence wizard, as opposed to continuing to the next step of the task sequence? It seems as though you would have to remove the USB media each time, whereas on a CD, it only boots to the media after you "press any key to boot to CD." Anyone have a workaround for this? What is everyone else doing?
  8. Hello, To start with some info. Our company runs SCCM 2007 R3 and we are migrating all XP machines to 7x86. All computers that are connected to the network by a fast or medium LAN/WAN connection run fine with the use of one primary and a couple of secondary sites that initiate OSD by Client or PXE. The problem that I have exists only to the small slow WAN branch offices that we want to migrate using USB keys that are offcourse created with the TS Media Wizard. So far everything works splendid as the image deploys nicely and when done SCCM does the rest. The problem I have is that the client computers will have a computername set like MINNT-XXXX And I want them to just use the AD Computernames like they had. Computer AB12 should have the same name after migration. All systems that install/migrate with Client OSD or PXE do this fine, only USB boot OSD's have this problem. Client or PXE OSD is not an option, it's no point in suggesting this as it is not in my hands. There must be something easy that I forget. Probably something to do with variables. The task sequence (relevant part) is build up pretty steight forward like this: Restart in Windows PE (var: _SMSTSinWinPE equals "false") Partition disk 0 (var: _SMSTSClientCache not exists) Apply Operating System Apply Windows Settings Apply Network Settings Etc. The only thing different is obviously that the first step "Restart in Windows PE" is bypassed as the computer boots from USB. therefore the variable _SMSTSinWinPE equals "false" might not run? don't get me wrong, I did not remove this step from the TS but my guess is that it will be bypassed automatically. The logs after deployment don't tell me much, only that the machine name is changed to MINNT-XXX and was "unknown" telling me it probably was unable to query WMI as the stage was bypassed and partitioning the disk already begun before that. Is there something easy i'm missing, skipping etc.. ? I'd rather not use to much VBS but if there is no other solution I'm open for suggestions, although im not good in scripting. With Kind Regards, Jeffrey
  • 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.