Jump to content


Search the Community

Showing results for tags 'wds'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

  1. Hello all. I am new at using WDS, so please bear that in mind. I have a Dell Laptop, Windows 7 x64 on it. I have WDS set up on a Server 2003. I have successfully imaged XP and Vista machines, and pushed the images onto other PCs. Two questions: 1: I am trying to capture an image from the Dell. When I PXE boot it (is that the correct term?), I see Vista as an option to select, but don't see Microsoft Windows Setup (x64). I do have that as an option in my WDS boot images. So, why is this happening? I created an image using Vista, it ran with no errors. I haven't pushed it out to another laptop, yet. 2: When I PXE booted, I wanted to save the image to my server. Couldn't do it, the local machine could not see the server, I had to save the image onto the Dell's hard drive. Ideas? Questions? I know that I can only run Sysprep three times, so I haven't done much experimentation. Thanks for your help, Scott
  2. Hi all I have had WDS and PXE running quite happily for a few months, but all of a sudden it has stopped working. WDS is installed on a member server DNS & DHCP on a seperate server Everything is on a single VLAN Set to accept known & unknown What I seem to be getting on 2 site is "pxe-e55: ProxyDHCP service did not reply to request on port 4011" I've been looking around (including this forum) and can't quite find the same scenario. This is a very basic setup - what am I missing? It was all working without any issues until recently. Have there been any patches to Win2k8R2 that would affect it? Any advice would be very gratefully received! Thanks in advance Rich
  3. Hi Everyone- This is my first time posting here, but I visit this site almost every day and always find good info, so hopefullly you can help me uncover some of the issues i have created for myself. I have a single server SCCM environment that was working well to deploy software, manage endpoint protection and handle computer images/pxe boot through WDS. Yesterday, I installed the Dotnet 1.1 framework on the server as a prereq for some other software, and everything blew up. My event log filled with IIS errors 2274 and 2268 over and over again. I ripped out Dotnet 1.1, but that really didn't help. My current issues: Application Deploy has stopped working. I can setup deployments all day long but my clients don't see them. PXE/WDS and SCCM are not communicating My troubleshooting steps to this point: Ripped out Dotnet 1.1 Uninstalled all roles (IIS & WDS) Repaired Dotnet 4.0 Reparied MDT Removed the Distribution point role from my server Reinstalled IIS and WDS Re-added the DP role Notes: At this point, I can boot from PXE if I manually put the boot.wim in to the boot folder of the WDS console, but it fails to connect to SCCM and reboots after WinPE is loaded I did point the WDS role to my D:\remoteinstall folder (the one I have used all along) I am worried about other side effects that I have not yet realized. SCCM uses IIS (WebDav) to manipulate AD, correct? What other things did I break? There are so many log files, i have no idea which ones are valuable and which ones are going to send me off chasing my tail. I really, really, really, really wish i had made a snapshot of the SCCM server before installing Dotnet 1.1 Thanks in advanced for any advice you can give.
  4. Hi, I am having trouble with my WDS Server PXE on only my desktop computers. I can PXE boot my laptops and image them just fine, but get an error when trying to deploy my desktop computers. The WDS is on a hyperv server and has a static DHCP. Please Advise.
  5. Hi, We have been happily using WDS to capture Windows 7, server 2003 & server 2008 & deploy these with great success. However we have a requirement to capture an existing server 2008 with multiple partitions & redeploy Everything I have been reading says it can't really be done successfully with WDS. Server Setup:- Windows Server 2008 OS - C:\ 68.3 GB Program Files - E:\ 136Gb Program Files - F:\ 136Gb SO as you can see above we need to capture all partitions & deploy successfully. Can anyone advise if that have successfully completed this task. Thanks 2scoops
  6. I Set up SCCM 2012 RTM, and have been fighting with deploy and capture for a few days. I successfully imported an Operating System Installer I successfully created a task sequence I I was able to get the machine to PXE boot, and it almost loaded windows PE; however, I kept getting the following error message: Windows PE cannot start because the actual SYSTEM ROOT directory (x:\windows) is differrent from the configured one (x:\$windows.~bt\windows). This can be configured from dism.exe with the /set-target path command. please refer the documentation for more details I was able to trace this problem back to using a boot.wim file other than the one included with SCCM / WDS. I had deleted the original boot.wim files, and used one from a windows 7 install cd. To resolve the problem, i used dsim.exe to modify the boot image: C:\sources\os >mkdir wim C:\sources\os>dism /mount-wim /wimfile:boot86.AAA0001c.WIM /index:1 /mountdir:wim C:\sources\os>dism /image:wim /set-targetpath:X:\ Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Target Path : X:\ The operation completed successfully. C:\sources\os>dism /unmount-wim /mountdir:wim /commit Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image File : C:\sources\os\boot64.AAA0001b.WIM Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. C:\sources\os>copy boot86.AAA0001C.WIM c:\RemoteInstall\SMSImages\AAA0001C\ Overwrite c:\RemoteInstall\SMSImages\AAA0001C\boot86.AAA0001C.WIM? (Yes/No/All): y 1 file(s) copied. After these commands, I was able to boot into launching the Task Sequence to Build and Capture my windows 7 image (Don't mind the x86/x64 difference from the screenshot and the commands above, I had to do the procedure twice...once for each boot image) However, after the Build and Capture, I was again presented with the same error I rebooted into the PXE WinPE (F12 network boot), and launched command prompt (F8 if you have enabled it within the SCCM image): I repeated the same procedure as I did on the PXE boot image for the local image, but first i had to find out where the local image was: X:\sms\bin\i386 >bcdedit Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} timeout 30 Windows Setup ------------- identifier {default} device ramdisk=[C:]\_SMSTaskSequence\WinPE\sources\boot.wim,{ra mdiskoptions} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[C:]\_SMSTaskSequence\WinPE\sources\boot.wim,{ra mdiskoptions} systemroot \windows nx OptOut detecthal Yes winpe Yes My local (hard-disk) image is in =[C:]\_SMSTaskSequence\WinPE\sources\boot.wim, So I ran the same commands against that file: C:\_SMSTaskSequence\WinPE >mkdir wim C:\_SMSTaskSequence\WinPE\sources>dism /mount-wim /wimfile:boot.wim /index:1 /mountdir:wim Deployment Image Servicing and Management tool Version: 6.1.7601.17514 Mounting image [==========================100.0%==========================] The operation completed successfully. C:\_SMSTaskSequence\WinPE\sources>dism /image:wim /set-targetpath:X:\ Deployment Image Servicing and Management tool Version: 6.1.7601.17514 Image Version: 6.1.7601.17514 Target Path : X:\ The operation completed successfully. C:\_SMSTaskSequence\WinPE\sources>dism /unmount-wim /mountdir:wim /commit Deployment Image Servicing and Management tool Version: 6.1.7601.17514 Image File : C:\_SMSTaskSequence\WinPE\sources\boot.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Then I rebooted and everything continued along happily
  7. Hi everybody, Here is My scenario, I have WDS running on a Server 2008 R2 Machine, and have been succesfully imaging XP machines for a while now. I am trying to setup a Windows 7 amd64 image on it, and it doesn't appear to like my unattend.xml, ie, it doesn't get the language options that I have set in the unattend,.xml, it doesn't automatically load the right image off WDS, which is also specified in the unattend.xml etc. The thing that I think may be causing the problem is that the Boot image I am using in WDS is the x86 boot image that we have been using to image the XP machines. Do I need to create an amd64 boot image for it to recognise the amd64 commands in the unattend.xml? The Windows 7 image itself works fine, but for simplicity sake, because I'm going to have to do over 100 of these in the coming months, I would prefer to make it and unattended installation. This has been driving me nuts the last couple of days. Edit, here is my WDSclientunattend.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration> <Disk wcm:action="modify"> <ModifyPartitions> <ModifyPartition wcm:action="modify"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>SysVol1</Label> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> <WillShowUI>onerror</WillShowUI> </DiskConfiguration> <WindowsDeploymentServices> <ImageSelection> <InstallImage> <Filename>XT3_WIM.wim</Filename> <ImageGroup>Consultant_Laptop</ImageGroup> <ImageName>XT3_WIM</ImageName> </InstallImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> </ImageSelection> <Login> <Credentials> <Domain>Domain.com</Domain> <Password>Password</Password> <Username>Username</Username> </Credentials> </Login> </WindowsDeploymentServices> </component> </settings> </unattend> -Mark
  8. Hi, I have WDS on Win2008 R2. Doing upgrade job on server farm from Win2008 to Win2008 R2. Have built an image as I want it and captured it. When re-imaging the servers that are on the domain they hold their hostname and rejoin fine which is perfect, I just have to change the ip address. But when I use a server that has been removed from the domain and computer account has been deleted or it's just brand new server, then I just get the change Admin password after it's deployed and it's in workgroup. How do I set this up so I can use the same image for existing domain servers and new servers I introduce to this domain? I'm thinking I need to have 2 images one as it is and the other a copy with an answer file. Thanks
  9. We have a forest domain with 2 child domains. Each child domain has it's own WDS server, and each child domain runs on their own subnet (child-domain-1: 10.100.x.x range, child-domain-2: 192.168.x.x range). Both of these networks are bridged too, so we can communicate with one another. When we image machines within child-domain-1, clients sometimes boot to the WDS server of child-domain-2. It takes quite a few reboots/on-offs to get to boot correctly. Is there anyway to correct this? child-domain-1 clients should ONLY boot to the WDS server of child-domain-1, and child-domain-2 clients should ONLY boot to the WDS of child-domain-2. It's quite annoying, and I've configured each to only connect to their respective domains.
  10. Has anyone else experienced this? Event Logs only showing it terminated unexpectedly.
  11. We have over 100 remote sites connected with a 1.5mb connection. Currently, we use Zenworks for pc management. One feature we use is automatic re-imaging. When a remote computer needs to be re-imaged, we assign the task in zenworks. The computers are set to PXE boot first. When this job has been set, the pc boots, sees the task and completes it. This has been easy to reproduce with SCCM (We are migrating from Novell to Microsoft). The hard part is when the machine re-images, it applies the image from a second partition on the local hard drive. I can't figure out how to do this with SCCM. It takes too long to push the image over the network. Since we only have 3 to 5 users in each office, I can't justify a separate machine as a distribution point. Any help would be greatly appreciated.
  12. Good Morning Folks, I'm hoping someone can shed some light for me. I'm wondering how many folders should live inside of the Remoteinstall folder? I currently only have 3 which are SMSBoot, SMSIMAGES, and SMStemp. I noticed that in my other Remoteinstall folder that have been renamed Remoteinstall.old that there are about 5 or 6 more folders. I ask this because I recently had to re-install my PXE Service Point on my Primary server as it was being somewhat flaky and had some errors in the SCCM System Status Node. I followed the guide from here , uninstalled/reinstalled and thought I was good to go. Later on I tried re-imaging a computer, I was able to boot from PXE ( recieved the x64 boot image ) but I recieved the following error after about 30 minutes or so at the step "Setup is Applying System Settings" "Windows could not parse or process the unattend answer file for pass {specialize}. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Windows-Shell-Setup]" I've used this image and task sequence multiple times in the past and everything went smooth so I'm not sure why I'm now facing this issue. Can anyone guide me in the right direction? Thanks for your time.
  13. I'm trying to troubleshoot one of my labs which is having all sorts of PXE issues. I'm comparing it to my other lab that i have functioning. In some of the articles i'm reading, they suggest that i TFTP from command line to test if its working. Well, it isn't in either case and i'm beginning to wonder if it is supposed to and if this troubleshooting step is applicable/viable. Could someone confirm if this is working in their SCCM 2012 setup? Basically what i'm doing is running this command from my DC for example to my SCCM server (distribution point). tfpt -i 192.168.x.x GET \smsboot\x64\pxeboot.com You will need to add TFTP client from the windows features in server manager.
  14. Couple of issues that I can't quite remember when dealing with sysprep. 1) I have a couple images that aren't to be joined to our domain, yet when I set <JoinWorkgroup>WORKGROUP</JoinWorkgroup> in sysprep.xml AND in WDS I select "Do not join the client to a domain after an installation", it still ends up connecting to the domain. 2) I'm noticing in the registry, the original computer name that had been sysprepped and captured was still showing up. I used: sysprep.exe /oobe /generalize /shutdown I can't recall if this is just how it happens or if it's supposed to be like that.
  15. good morning everyone. i am in the process of trying to get WDS to work in out live environment. everything works like a charm in the test lab and it is time to move over to live. i have run into a strange issue when PXe booting a PC. well first it does not pxe boot. however i do not get any errors. the PXE boot screen looks like this. CLIENT MAC ADDR (mac address shown) GUID (guid shown) DHCP............................................................................... ........................................................................................ this will go on for as long as i allow it to before hitting esc. so here is what i know. server 2k8r2 DHCP is on different vlan then WDS option 60 and do not listen on port 67 are UNCHECKED on DHCP tab in properties of WDS DHCP and WDS servers have different IP but same subnet all ports on routers are open. if you need any further info please ask. i will be watching this thread for the next 3.5 hours then off and on for the rest of the day. thank you in advance.
  16. Hi there, I'm pretty new to SCCM so this might be an easy problem. A couple of days ago our Operating System Deployment stopped working. The first sign of that something was wrong was that the WDS service couldn't be restarted. It hung. Even after a reboot of the entire server the service was still not running. After a lot of troubleshooting we also noticed that the image-folders under RemoteInstall\SMSBoot\x64 and RemoteInstal\SMSBoot\x86 were empty. I then got some advice that I should delete the PXE role in SCCM and re-install the WDS service in Windows. So I did: 1) Removed PXE role. 2) Uninstalled WDS. 3) Reboot. 4) Finalize uninstall. 5) Reboot again. 6) Renamed the folder "RemoteInstall". 7) Installed WDS. 8) Rebooted. 9) Added the PXE Role. 10) Rebooted. This i have done twice, the main issue is still there, the folders are still empty. when I try to deploy a PC I just get the error: "PXE-M0F: Exiting Intel Boot Agent". The client recieves an IP from the DHCP but there is no boot-image. In the logfile: pxeMSI.log.LastError i found the following row: "MSI (s) (B0:00) [10:50:25:911]: Windows Installer removed the product. Product Name: SMS PXE Service Point. Product Version: 4.00.6487.2000. Product Language: 1033. Removal success or error status: 0." In the logfile: pxeMSI.log i found the following rows: Property(S): UserExitDialog_Title = Setup Aborted Property(S): UserExitDialog_SubTitle = Setup was cancelled Property(S): UserExitDialog_Info = The SMS PXE Service Point setup was cancelled. Property(S): InstallErrorDialog_Title = Setup Aborted Property(S): InstallErrorDialog_SubTitle = Setup failed Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue. I have also attached PXESetup.log. Any suggestions and/or pointers would be greatly appreciated. Thanks! PXESetup.log
  17. Hi guys, I stumbled across this site through google and I think this might be the best place for me to ask some broad (as well as some very pointed) questions about the whole thing. First off, this acronym soup is killing me. I've got a pretty healthy list of things I need to remember now. With that being said, here is what I currently am doing to deploy Windows 7 to our computers (Mostly Dells): 1. Use MDT to add applications, out-of-box drivers (organized into Operating system, then machine model), and a custom task sequence to rename the primary partition "Local Disk". 2. Add the Lite Touch iso created by MDT into WDS. Do a normal WDS deployment via PXE So my questions really are these: 1. Is this a reasonable way to do it? 2. How can I improve it to make it as automated as possible? 3. Where does WSIM come into play? I would love to be able to define some settings, but also they very from computer to computer slightly. Can I create multiple autounattend.xml files that all use the same install.wim file? 4. How can I set the computer name automatically to be the dell service tag during install instead of declaring it during the Deployment Wizard? 5. How do I update my install.wim file with new Windows Updates offline (by NOT installing Windows onto a reference machine and capturing a new wim file)? 6. In a general sense, can I continue to do most things in MDT and then use WDS to actually push the OS out? Is that the standard method? Thanks! Brian
×
×
  • 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.