Jump to content


boozecow

Established Members
  • Posts

    17
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Montreal

boozecow's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Little trick I found: Try to create a Task Media with your Task Sequence. If you pass all the screens, all the packages are available from distribution point. If there is a missing package, corrupted package or missing distribution point, it will tell you.
  2. I would answer, stop WDS on your SMS sites as emergency !!!
  3. Just want to add some notes from this wonderfull guide. For example. I have a server HBM-WSUS and my SMS site name is SMS-MST The Software Update point have to be install on BOTH server, not only on the HBM-WSUS. I lost some time figuring this out and asking me why the synchronisation failed. The WSUS 3.0 SP2 administration console need to be installed on the SMS site. Logs file for this is located in : SMS\LOGS\WSYNCMGR.LOG Thanks again for the guide !
  4. On the server where your PXE and WDS are install (SMS Server) If the configuration as been done correctly, you should see on your temp directory: c:\windows\temp\PXEBootFiles Stop WDS, Delete all files in c:\windows\temp\*.* Give full rights on c:\windows\temp\*.* Delete or rename your sms_ccm\logs\smspxe.log start WDS When I start WDS, the directory c:\windows\temp\PXEBootFiles is created Look at your smspxe.log You should see lines like: Opening image file D:\RemoteInstall\SMSImages\SMSPKG\MTL00021\boot.MTL00021.wim Applying image 1 to volume C:\Windows\TEMP\PXEBootFiles Closing image file D:\RemoteInstall\SMSImages\SMSPKG\MTL00021\boot.MTL00021.wim If it is not working... there is a TID on the site on how to rebuild your PXE. From memory it's. Remove the WDS role, Remove PXE from SMS server role, reboot Add the WDS role back to your server and DO NOT CONFIGURE IT Add the PXE role back to your SMS server role. Ho, BTW, did you add distribution points "\\sms\smspxeimages$" to your "Boot image X64 AND X86" under Operating System Deployment | Boot Images section ?
  5. I find my answer trying to create a task media with my task sequence. I was not able to create my task media (error that report missing package...) One of the package has a corrupted Distribution Point entries...I saw it from the system status | Site status | sms_distribution_manager. I deleted this package, recreate it and I'm now back on track. Error was: SMS Distribution Manager failed to process package "W7 Language Pack French " (package ID = MTL00015). Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
  6. The only suggestion would be to look at your SMS_CCM\LOGS\SMSPXE.log again... When the WDS start, it copy the boot.wim file to your c:\windows\temp On your SCCM server where WDS and PXE are running: Stop WDS, Delete your c:\windows\temp\*.* Be sure SCCM have full rights on your c:\windows\temp\*.* Delete the file SMS_CCM\LOGS\SMSPXE.log Start WDS Check your wim file as been created to your c:\windows\temp\ Check the SMS_CCM\LOGS\SMSPXE.log Check with wireshark that your PC receive the wim file. If not working, I guest you will have to review your installation. There is good guides on this site.
  7. I'm facing a strange problem, my task sequence stop working when I'm adding steps to it... As soon as I add "install software" (at some point, not always at the first one) steps into it, the task sequence stop at the task "Restart in Windows PE" Wondering if anybody else experiented this issue ? Task Sequence resume: Install Operating System Restart in Windows PE (Restart Computer with boot image assigned) Partition Disk (Format and Partition Disk) Apply Operating System (Apply Operating System Image) Apply Windows Settings (Apply Windows Settings) Custom Drivers New PC Apply Device Drivers (Auto Apply Drivers) Setup Operating System Setup Windows and configMgr (Setup Windows and ConfigMgr) Deploy Applications SCCM Toolkit Version 2 (Install Software) W7 Language Pack French (Install Software) Microsoft Office 2010 (Install Software) Ms Office 2010 French LP (Install Software) DOT NET 4.0 (Install Software) Drivers Software Vmtools Soft Drivers (Install Software) Add PC to Domain HB JoinDomain Command Line) Restart Computer
  8. << my client machine does not receive a Client IP address once it boots up from PXE >> All depend how you configure your network but if your PXE server is located on a different server than your DHCP server, you will have to configure your switch and setup your vlan to forward the REQUEST to both your PXE server and your DHCP server. You maybe need to add the option 66 to your DHCP server too. And when you add the PXE service to your sms server, look at the logs file : SMS_CCM\LOGS\SMSPXE.log for any queue. Me, sometime, when I advertise my task sequence to computers, I need to restart the service "Windows Deployment Services Server" to force the PXE server to reload the mac tables from the SQL database. If you can't find anything from the logs, install "Wireshark" to your SMS and DHCP server and capture the packet while booting your workstation to see if your DHCP and PXE server receive and answer to that request.
  9. boozecow

    SCCM questions

    I'm not an expert of SCCM but I currently have a task to upgrade our SMS to SCCM. I have Two major sites and few regional sites. My setup is: One central site Major Site 1 - Primary (600 users) Secondary Site 1 (70 users) Secondary Site 2 (140 users) Secondary Site 3 (45 users) Secondary Site 4 (30 users) Major Site 2 - Primary (0 user bunker site) Secondary Site 1 (120 users) Secondary Site 2 (600 users) Secondary Site 3 (80 users) Secondary Site 4 (5 users) On all secondary sites, I have like you a DC and a Fileserver I'm going to upgrade my secondary sites to windows 2008 + SCCM with WDS + PXE services. I will have one central image of windows 7 with multile task sequences for all the model of the computers I have in the compagny. All regional site will respond to his PXE local services and will get the image from the secondary site. So only one Image Nationaly distributed to local distribution point. If you want to sleep at night and keep control, I think you should do this. But let's see what expert will say about this !
  10. Ha, Look for simple solution first. I'm going to remove the language pack from the reference image and add it inside a Task Sequence... You can install any language pack with a simple command line: Dism /online /Add-Package /PackagePath:LangPacks\fr-fr\lp.cab
  11. Hi, I'm having an other question. When I deploy my Reference image (Windows 7 Ent with the Language Pack installed.) The Deployment task sequence pause when this screen appear << Set UP Windows Ma langue est: francais My language is English. >> I have to manualy select the language and click next, after that my task sequence complete successfully. I want to automate this task but since I'm pretty new in this world of workstation deployment, I have no idea where to start looking at... Is it at the task sequence "Apply Operating System" and at the section "Use an unattended answer file" I have to work on... ?
  12. Finaly, I'm using a VBScript and running it as a task sequence. Working nice. It's not perfect because I'm now having a password in clear text inside a file but at least I'm now having a work around. Const JOIN_DOMAIN = 1 Const ACCT_CREATE = 2 Const ACCT_DELETE = 4 Const WIN9X_UPGRADE = 16 Const DOMAIN_JOIN_IF_JOINED = 32 Const JOIN_UNSECURE = 64 Const MACHINE_PASSWORD_PASSED = 128 Const DEFERRED_SPN_SET = 256 Const INSTALL_INVOCATION = 262144 strDomain = "Domain.CA" strPassword = "Passw0rd" strUser = "User" Set objNetwork = CreateObject("WScript.Network") strComputer = objNetwork.ComputerName Set objComputer = GetObject("winmgmts:{impersonationLevel=Impersonate}!\\" & _ strComputer & "\root\cimv2:Win32_ComputerSystem.Name='" & _ strComputer & "'") ReturnValue = objComputer.JoinDomainOrWorkGroup(strDomain, _ strPassword, strDomain & "\" & strUser, NULL, _ JOIN_DOMAIN + ACCT_CREATE)
  13. I'm new and I successfuly create a reference image following guides from this forum. I'm trying to deploy this reference image and the only task none working for me is the task "Apply Network Settings" Here the resume of my Task sequence: Install Operating System -. Restart in Windows PE -. Partition Disk -. Apply Operating System -. Apply Windows Settings -. Apply Device Drivers Setup Operating System -. Setup windows and configMgr -. Apply Network Settings At the end, my PC are not in the domain and on the smsts.log I have: Successfully complete the action (Apply Network Settings) with the exit win32 code 0 So doens't looks like to have any usefull error I can work on. The task Apply Network Settings is really basic: Join a domain: Domain: Mydomain.ca Domain OU: LDAP://CN=Computers,DC=Mydomain,DC=ca Any hint for me where I can work in to make this working ? Thanks in advance for any help ! smsts.txt
  14. Don't know what will be the impact yet but I'm doing this for now and it is working... I'm building a windows 7 and create a regular account like HBUser. I configure all the settings I want for my users. At the end, I modify the registry key: HKEY_LOCAL_MACHINE\Software\microsoft\windows nt\CurrentVersion\ProfileList I changed the value of the Default key to %SystemDrive%\Users\HBUser Working like a charm. But since I'm a noob, let's see what you are thinking about this ! Well, after few test, I had to say that something the profile service fail to create the profile, no good...
  15. Ok, I finaly make it working... Anstead of pointing my destination wim file to \\sms\source... I create an other share folder on an other server and point the wim file there. Working... So It must be a security issues... This SMS server was running 2003 with SMS... I upgrade the server to Windows 2008 + SCCM SP2... (Take me 1 week to solve all the issues...) I will wait until my image done and will try to get this c:\windows\temp\sms*.log file... Thanks for your help !
×
×
  • 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.