KuifJe
-
Posts
31 -
Joined
-
Last visited
Everything posted by KuifJe
-
Judging by the logs its a DNS issue, closer study of the ipconfig of the machine showed it was using IPv6 adresses for DNS. This is a tad troublesome seeing I disabled all IPv6 functionality in our network.
-
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>3621dd4d-2bf0-49a1-a9f2-7f15dbe58cd7</SourceID><SourceHost/><TargetAddress>mp:[http]MP_ClientIDManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-06-23T00:28:46Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="306"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_ClientIDManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSPxe 6/22/2009 4:28:46 PM 1304 (0x0518) CLibSMSMessageWinHttpTransport::Send: URL: W2K8-SCCM.xxx.xxx:80 CCM_POST /ccm_system/request TSPxe 6/22/2009 4:28:46 PM 1304 (0x0518) Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 6/22/2009 4:28:46 PM 1304 (0x0518) unknown host (gethostbyname failed) TSPxe 6/22/2009 4:28:46 PM 1304 (0x0518) hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 6/22/2009 4:28:46 PM 1304 (0x0518) sending with winhttp failed; 80072ee7 TSPxe 6/22/2009 4:28:46 PM 1304 (0x0518) Will retry in 6 second(s) TSPxe 6/22/2009 4:28:46 PM 1304 (0x0518) Retrying... TSPxe 6/22/2009 4:28:52 PM 1304 (0x0518) This is the part in the log where it goed wrong. I tried the F8 option, but that shows me connectivity to all relevant servers. Will google this and see if I can get somewhere, any help still appreciated though ;-)
-
I've followed the deploy Vista steps untill step 5. And then the frustrations are piling up... To start off, the machine I'm using to build and capture a Vista image is a virtual machine build on Hyper-V. I've created a VM with a 40 GB disk, 2 procs and 512MB memory. It's also configured for PXE boot. That's not the problem really, I've booted into the PE environment countless times. However if the machine is done booting into PE it will reboot itself (after aprox. 6 minutes) it will then continue to abortpxe.com and fail to boot all together. Only way to get it going again is to clear the PXE boot advertisement and let it go at it again. This will start the above procedure all over again... Any ideas? What .log could give me a clue as to what is happening? :angry: [edit] I've used an IDE drive for the VM so that shouldnt be a problem either [/edit]
-
Thanks for the swift reply... I'm a bit stumped though. I'm certain I've read somewhere you shouldn't manually configure WDS, just install it and then let SCCM do the rest Ah well, on with the show and see what happens. That's probably why it's called a lab environment
-
I'll start of by saying this is by far the most clear and descriptive site when it comes to installing and troubleshooting for SCCM, good job! I'm currently in the proces of setting up a test lab (1 DC, 1 SCCM server, 1 SQL server). Eventually our goal is to get OSD, updates and software distribution working with SCCM 2007 R2. Your setup and installation procedure for SCCM work like a charme. However when I come to the OSD bit I miss the specifics on what extra software is needed. I've come across posts (not on this forum) stating MDT isn't a prereq and neither is WDS Can anyone here specify what software/features/roles exactly are needed and in what order these should be installed to get the most out of OSD in R2 of SCCM 2007? Base software allready installed: Windows 2008 Domain All Windows 2008 servers Windows SQL 2008 Standard I'm not looking for the complete walkthroughs of the installations, those aren't the issue, it's teh exact software prereqs I'm looking for. Thanks in advance
-
Very nice site, and Google was nice enough to point it out to me ;-) A great help in installing SCCM R2 on Windows 2008, keep up the good work!