Installed MDT 2008 and SCCM 2007 R2 and I created a .wim image file for OS deployment via SCCM 2007 R2 but i dont get any progress even at the first step as booting from network.
And i got following error message on client PC
PXE-T01: File not Found
PXE-E3B: TFTP Error - File not Found
I searched many blog and technet but i dont find any resolution for this problem. And then, i started to try everything that all troubleshooting methods, many log files, many tools and at last, i solved it as following:
1. Installed SCCM
2. Isntalled WDS and disabled any response client PC's
3. Installed DHCP
4. Already, boot image files is ready no any action for boot files
5. I created DP for boot image files
6. I created a .wim file on Operationg System Image then distributed any DP.
7. I created a task sequence and then advertised via right clicking
8. And more important point: You create a machine definition on Computer Association that included MAC Address and GUID (you can find this at startup screen or DHCP)
And unbelievable, amazing :) my client pc connected to TFTP and booting my boot.wim file no any problem.
More: www.mshowto.org
Saturday, March 28, 2009
Extending Virtual PC Image Files (e.g: .vhd files)
How can we extend our virtual pc's. I was searcing a way and found a 3 party software that named VhdResizer (if you want to download this, you click to these).
For use program, You basicly install your computer with next next next... and then, start program and then click browse button for open your wanted to extend .vhd file.
Everything is ok at this point but actually your .vhd file is still at old capacity. Following steps is explaining for resolution:
You define your extended .vhd file as secondary disk on any different Virtual PC. Then, Start this VPC, and after started the windows, you start a command promt and write following commands:
1. CMD --> Enter
2. Diskpart --> Enter
3. List Volume
4. Select Volume (Select you want to extend volume number)
5. extent --> Enter
6. Commit changes before shuted down VPC
And at the last section you can use this extended .vhd file properly.
More: www.mshowto.org
For use program, You basicly install your computer with next next next... and then, start program and then click browse button for open your wanted to extend .vhd file.
Everything is ok at this point but actually your .vhd file is still at old capacity. Following steps is explaining for resolution:
You define your extended .vhd file as secondary disk on any different Virtual PC. Then, Start this VPC, and after started the windows, you start a command promt and write following commands:
1. CMD --> Enter
2. Diskpart --> Enter
3. List Volume
4. Select Volume (Select you want to extend volume number)
5. extent --> Enter
6. Commit changes before shuted down VPC
And at the last section you can use this extended .vhd file properly.
More: www.mshowto.org
Saturday, March 07, 2009
Blue screen issue when using the Hyper-v at random times ( hvboot.sys )
I have got a little problem related hyper-v but no any log on event viewer. No any resolution after basic searching at google or yahoo and I decided to research dump file at c:\windows\dump.dmp. I installed Windows debugging tool and ran following command:
!analyze -v
and after this command i took following output:
FOLLOWUP_IP: hvboot+2792fffffa60`07eab792 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: hvboot+2792
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hvboot.sys
And now i started to search from that point :) i searched a little and reached a hotfix, KB957967
http://support.microsoft.com/kb/957967/en-us
Ahh, I installed that hotfix and no any problem for ten days :) but maybe it should be done again :)
More: www.mshowto.org
!analyze -v
and after this command i took following output:
FOLLOWUP_IP: hvboot+2792fffffa60`07eab792 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: hvboot+2792
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hvboot.sys
And now i started to search from that point :) i searched a little and reached a hotfix, KB957967
http://support.microsoft.com/kb/957967/en-us
Ahh, I installed that hotfix and no any problem for ten days :) but maybe it should be done again :)
More: www.mshowto.org
Sunday, March 01, 2009
Error Message at OCS Mediation Server "The A/V authentication service cannot be contacted"
I have got following error message when i started mediation Server services:
"The A/V authentication service cannot be contacted. Connections that require firewall traversal will not be succesful"
For resolution, i checked all standart says, e.g communication port (5062), internal names of Edge and Front-End, but no any problem for that, like everything is ok! But source of problem is certificates on both edge servers and mediation server. I changed all name in certificates as including all external names and all internal names. And problem solved after restarted edge and mediation server services.
More: http://www.mshowto.org/
"The A/V authentication service cannot be contacted. Connections that require firewall traversal will not be succesful"
For resolution, i checked all standart says, e.g communication port (5062), internal names of Edge and Front-End, but no any problem for that, like everything is ok! But source of problem is certificates on both edge servers and mediation server. I changed all name in certificates as including all external names and all internal names. And problem solved after restarted edge and mediation server services.
More: http://www.mshowto.org/
Subscribe to:
Posts (Atom)