Jump to content


jrgonzalez_nyc

Established Members
  • Content Count

    18
  • Joined

  • Last visited

  • Days Won

    1

jrgonzalez_nyc last won the day on July 15 2015

jrgonzalez_nyc had the most liked content!

Community Reputation

2 Neutral

About jrgonzalez_nyc

  • Rank
    Member
  • Birthday 04/26/1984

Profile Information

  • Gender
    Male
  • Location
    California
  • Interests
    SCCM 2012, Operating System Deployment, Coffee, Sports

Recent Profile Visitors

462 profile views
  1. Thanks for the link Rocket Man. I'm not sure that the associate wifi script will work for us since we dont have the machine join the domain during the task sequence and we use certificate based wireless which is group policy. So, until the machine is actually joined to the domain and it gets its policy then it gets the wifi cert. Thanks for the feedback thadkew. We make the TS only available to Media and PXE so it is not available through software center. The only issue I could see here is if someone with permissions went in and set the Run behavior to Required and even then they would have to PXE boot and know the PW for our WINPE...but I see the concerns.
  2. Rocket Man, thanks for you reply! I understand that we can manually delete the resource/system that is created by SCCM and then refresh and it will work since it is unknown. It would be time consuming to go in and delete the records every time a technician uses one of these dongles to set up a computer. I'm still a bit confused regarding the 2nd question you asked. If I have the MAC address of the dongles ignored by CM via the registry key, doesn't it always ignore that MAC and thus use the BIOS GUID to deploy the task sequence? I thought the device is registered with SCCM using the BIOS GUID and on future refreshes it would be a known device? Please bear with me as I am still a bit confused by this process. After we image the machines using the dongle and join it to our domain, it registers in the inventory with its wireless mac. On future refresh I would imagine that it is a known device and should get task sequences that are deployed to the "All Systems" device collection?
  3. Hello Everyone, I am having a problem when trying to re-deploy an OSD task sequence to machines that have already been imaged. The machines are Dell tablets and we are reusing the same NIC dongles to image them via UEFI PXE booting. I have followed the steps from this article in order to reuse the same dongles: https://blogs.technet.microsoft.com/configurationmgr/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd/ Our OSD task sequence is deployed to the following collections: "All Unknown Computers", "All Systems", and "All Desktop Clients". Deployment settings are made available to "Only media and PXE" and Rerun behavior is set to "Always rerun program". It seem that when the technician takes a new tablet out of the box since it is seen as an unknown device in CM, it gets the available TS and they can image it. The problem occurs when they try to reimage the same machine, SCCM now sees it as a known device. However, whether the device is known or unknown shouldn't it be able to see the task sequence since I have it deployed to the collections mentioned above? Here is a snippet from my SMSPXE.log: Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:AA, 4C4C4544-0032-4D10-8052-B9C04F474332: device is in the database. Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID>GUID:62efbe3a-9224-4a5a-a2c5-63d6fb7b1190</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> 00:50:B6:17:6D:AA, 4C4C4544-0032-4D10-8052-B9C04F474332: found optional advertisement CM12000F Looking for bootImage CM100005 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID>GUID:62efbe3a-9224-4a5a-a2c5-63d6fb7b1190</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> I noticed that when the machine is unknown the SMSPXE.log looks like this: Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:7E, 4C4C4544-004D-3610-8052-CAC04F474332: device is not in the database. Getting boot action for unknown machine: item key: 2046820353 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>e2b9e21e-4a0f-40d6-94eb-6ebf20a22d59</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> 00:50:B6:17:6D:7E, 4C4C4544-004D-3610-8052-CAC04F474332: found optional advertisement CM12000F Looking for bootImage CM100005 Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:75, 4C4C4544-0053-4710-8052-B8C04F474332: device is not in the database. Getting boot action for unknown machine: item key: 2046820353 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>e2b9e21e-4a0f-40d6-94eb-6ebf20a22d59</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> Any ideas why it wont see the task sequence? Thanks! Joe
  4. Whats the deal with no DHCP tools?!?!
  5. Hello, I am running Windows 10 x64 Educational version on a virtual machine. My co-worker is running the same version on his physical box. We have both noticed that Windows 10 cannont connect to our Hyper-V host which runs on a windows 2012 server core machine. We get the following error: "An error occurred while attempting to connect to server xxxxx. Check that the Virtual Machine Management service is running and that you are authorized to connect to the server." The service is running just fine and our accounts are domain admins and have sufficient rights to connect to the host since we are able to do it from our Windows 8.1 machines. Could this be due to Hyper-V version mismatch? Do I need to change more permissions on the server core firewall? Please, any advice would be greatly appreciated. Regards, Joe
  6. Thanks Niall for always keeping us up to date. I usually come here first for all my SCCM issues. Do you know if we will still need Johans workaround as well, ( http://deploymentresearch.com/Research/Post/443/Beyond-unsupported-Deploying-Windows-10-preview-including-drivers-with-ConfigMgr-2012-R2 ) in order to get drivers to deploy during OSD? Or will the CU1 patch take care of this as well? Best Regards, Joe
  7. Hi, please post your smspxe.log.
  8. Just wanted to update this forum with the solution that worked for me. Initially after the upgrade I received calls regarding imaging, but then I noticed there were more problems specifically with our Management Point. My issues had to do with figuring out what was hosing our Management Point. This thread helped me out tremendously: https://social.technet.microsoft.com/Forums/fr-FR/eb21f07a-6d01-4e61-bb6b-97a47626d78a/errors-after-update-from-sccm-2012-r2-to-r2-sp1?forum=configmanagergeneral Trend Micro was causing problems with some of the services. After we uninstalled Trend Micro and removed and re-added the Management Point Role, everything seems to be working pretty smoothly. My advice if your going to upgrade to 2012 R2 SP1 is to make sure you disable your anti-virus before running the installer.
  9. We just finished upgrading our SCCM Servers both our CAS and PS1 to SCCM 2012 R2 SP1. After the upgrade it seems that the new boot.wim file that is created is having issues. After the machine pxe boots and pulls down the wim file, it goes to windows is starting up then preparing network connections and then black screens and restarts. I opened up an F8 command prompt and pulled the SMSTS.log and I see an error during the TSMBootStrap.exe step. The error is Failed to download pxe variable file ... PxeGetPxeData failed with .... I have attached our SMSTS.LOG file. I verified that i have network connectivity by running IP config and then I was also able to ping our MP. I thought it might be driver related but I have tested from different dell models, Dell 9020, E3340, 7010, etc. and they all have the same problem. Any ideas/suggestions? smsts.log
  10. Thanks for the feedback. I contacted our Dell rep regarding this as well and he also suggested using Windows 8 and onward with UEFI. The good news is with all the research and time we have already spent testing, our manager decided to hold off on UEFI until we get Windows 10! Thanks for all the step by step guides you provide Niall. They really are helpful.
  11. Hello just to follow up on this thread I wanted to post what I have tried: I created a Windows 7 x64 SP1 CD as well as a Windows 8.1 x64 CD. I set the BIOS to UEFI and tried installing Windows 7 directly from the disk and it freezes. I set the BIOS to UEFI and tried installing Windows 8.1 from disk and it succeeds. It looks like this might definitely be an issue with Dells BIOS not working nicely with Win 7 and UEFI. Has anyone been able to image a Dell machine with Win7 and UEFI? If so, how did you guys do it?
  12. Hi Tim, I also read the following regarding other Dell Models: "We use MDT 2013, and UEFI on our systems. We have found, if Legacy Option Rom is disabled imaging always comes back as unable to read the partition after pushing the captured image. "0xc000000d An error occured while attempting to read the boot configuration data." Similarly, if you try to disable it after the machine is good, it will not be able to read the partition in the same way. This is only for the Windows 7 image. Never knew why, but as a result of this behavior disabling Legacy Option Rom isn't an option. Everything works peachy without legacy option rom on Windows 8.1 however (both during and after imaging)." Found on this thread: http://en.community.dell.com/support-forums/laptop/f/3518/t/19622501 However, I don't know if this a specific model issue because we have seen the same error on our Optiplex 7010's, 3020's, and 9020's as well as our Latitude E3340 model. I am going to test by setting the BIOS to UEFI and then imaging from windows 7 x64 disc just to determine whether its a hardware issue or our SCCM task sequence. I'll post what I find here.
  13. Just wanted to follow up with a little more info/details about this issue. I UEFI pxe booted again and before I ran the task sequence, I did the following: Hit F8, Entered Diskpart and cleaned the selected disk of any partitions. Ran the Task Sequence again and before letting it restart I entered Diskpart again and verified the following: Disk 0 shows an as asterisk under the GPT column as seen in your post here: http://www.windows-noob.com/forums/index.php?/topic/11135-why-do-i-get-a-winloadefi-status-0xc0000359-error-when-using-uefi-network-boot-in-system-center-2012-r2-configuration-manager. There are 4 Partitions, Recovery, System, Reserved, and Primary in that order. There are 3 volumes, Volume 0 = Letter C and it is the OS NTFS partition. Volume 1 = no letter and shows as Windows NTFS partition. Volume 2 = Letter S and shows as the FAT32 partition. Also, after I let the TS restart and got the BCD failure message again, I went into the BIOS and enabled LEGACY Options. After I did this, I restarted the laptop and it continues with the task sequence! Seems very odd to me. Any ideas?? Best Regards, Joe
  14. After the machine restarts to continue the task sequence, it gets the black screen error efi\bcd. Yes, I actually opened up a cmd prompt using F8 and then used CMTRACE to open up the smsts.log. I copied the log from the path you referred to and copied onto a usb drive. I do notice in the log file the following error after OSDdiskpart.exe: <![LOG[==============================[ OSDDiskPart.exe ]==============================]LOG]!><time="12:54:54.999+420" date="07-13-2015" component="OSDDiskPart" context="" type="1" thread="1064" file="main.cpp:1078"> <![LOG[Command line: "osddiskpart.exe"]LOG]!><time="12:54:54.999+420" date="07-13-2015" component="OSDDiskPart" context="" type="1" thread="1064" file="main.cpp:1079"> <![LOG[succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="12:54:54.999+420" date="07-13-2015" component="OSDDiskPart" context="" type="1" thread="1064" file="util.cpp:964"> <![LOG[Reading partition size info for partition 0]LOG]!><time="12:54:55.193+420" date="07-13-2015" component="OSDDiskPart" context="" type="0" thread="1064" file="main.cpp:461"> ............................ <![LOG[Reading partition size info for partition 2]LOG]!><time="12:54:55.193+420" date="07-13-2015" component="OSDDiskPart" context="" type="0" thread="1064" file="main.cpp:461"> <![LOG[Remaining size before partition: 499266388480]LOG]!><time="12:54:55.193+420" date="07-13-2015" component="OSDDiskPart" context="" type="0" thread="1064" file="main.cpp:465"> <![LOGLOG]!><time="12:54:55.193+420" date="07-13-2015" component="OSDDiskPart" context="" type="0" thread="1064" file="main.cpp:483"> <![LOG[set partition size: 134217728]LOG]!><time="12:54:55.193+420" date="07-13-2015" component="OSDDiskPart" context="" type="0" thread="1064" file="main.cpp:541"> <![LOG[Remaining size after partition 2: 499132170752]LOG]!><time="12:54:55.193+420" date="07-13-2015" component="OSDDiskPart" context="" type="0" thread="1064" file="main.cpp:618"> <![LOG[Failed to read filesystem from OSDPartitions2FileSystem, not formatting]LOG]!><time="12:54:55.193+420" date="07-13-2015" component="OSDDiskPart" context="" type="0" thread="1064" file="main.cpp:421"> Notice the Failed to read filesystem error. I assume this is the problem? Thank you so much for your help!
  15. I'm starting it via PXE. Shouldnt the TS set the disk to GPT mode when it runs the UEFI step?
×
×
  • Create New...