• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sacriestory

  • Birthday 01/13/1982

Contact Methods

  • MSN

Profile Information

  • OS
    Windows 7 x86
  1. Well, I answer to myself. Create a Profile in the mdt only with the necesary for the deploy. Create a Media task with the profile created. boot in pe mode. create a primary partition with around of 20 gigs of space. conect to the server and copy all the content of media in that partition. Enable boot from that partition with bootsect. Done. Start the computer and begin the task sequence process. the gather local script will detect automatically the partitions. At the end, the partition will be extend to the maximum and the deploy folders will deleted. Cheers.
  2. Hi Everyone, I need deploy some images with mdt 2010, the issue is deploy an offline image applied on the hard disk of those computers, so when the final user turn on the computer, the wim boot starts and ask to the user for the task sequence to deploy, without any media. How can do that? Thanks in advanced.
  3. HI everyone. I need deploy some servers but this servers have various sizes in disk How can I make Custom partition sizes in MDT 2010? I found this link but when I tried deploy this method but the ZTIUtility script fail somebody have a similar solution working on? thanks a lot
  4. Hi Guys, i have a geek question, somebody knows how Call the Network ID wizard directly from Shell? I can call system properties with this command: rundll32.exe shell32.dll,Control_RunDLL sysdm.cpl,,1 or C:\Windows\System32\SystemPropertiesComputerName.exe But the Network ID wizard can´t find it, I need it to deploy some computers outside the domain and later inside the domain and in the first run call the wizard. Somebody have any idea? invent or something. Thanks Brothers cheers B)
  5. Hi Guys. I Have a problem deploying a Custom Image. Specifically almost in te last part. here the log. <![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="13:20:54.412+300" date="08-24-2010" component="TSMBootstrap" context="" type="1" thread="3856" file="tsmbootstrap.cpp:1038"> <![LOG[Command line: "C:\MININT\Tools\X86\TsmBootstrap.exe" /env:SAStart]LOG]!><time="13:20:54.458+300" date="08-24-2010" component="TSMBootstrap" context="" type="0" thread="3856" file="tsmbootstrap.cpp:1039"> <![LOG[succeeded loading resource DLL 'C:\MININT\Tools\X86\00000409\TSRES.DLL']LOG]!><time="13:20:54.552+300" date="08-24-2010" component="TSMBootstrap" context="" type="1" thread="3856" file="util.cpp:869"> <![LOG[succeeded loading resource DLL 'C:\MININT\Tools\X86\TSRESNLC.DLL']LOG]!><time="13:20:54.599+300" date="08-24-2010" component="TSMBootstrap" context="" type="1" thread="3856" file="resourceutils.cpp:152"> <![LOG[shTSMBootStrapMutex.null() == false, HRESULT=8007051b (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1073)]LOG]!><time="13:20:54.614+300" date="08-24-2010" component="TSMBootstrap" context="" type="0" thread="3856" file="tsmbootstrap.cpp:1073"> <![LOG[Failed to create TSMBootStrap mutex (0x8007051B)]LOG]!><time="13:20:54.614+300" date="08-24-2010" component="TSMBootstrap" context="" type="3" thread="3856" file="tsmbootstrap.cpp:1073"> <![LOG[Exiting with return code 0x8007051B]LOG]!><time="13:20:54.614+300" date="08-24-2010" component="TSMBootstrap" context="" type="1" thread="3856" file="tsmbootstrap.cpp:1117"> Thanks In Advance.
  6. Perhaps somebody have the same problem. After googleit all day, I resolved it issue with this method On the server 2008 -Remove powershell from features. -Reboot -install powershell again. -Reboot -apply all patch from WSUS . So server is up to date. -reboot -Repair WAIK -Repair MDT 2010 -Reboot -and now it´s working strange and maybe far away for an offical method but works cheers
  7. Hi guys, My MDT server have a seriously problem; when I want rebuild my Deployment point I got the follow message. === Making sure the deployment share has the latest x86 tools === === Processing LiteTouchPE (x86) boot image === Building requested boot image profile. Determining if any changes have been made in the boot image configuration. No existing boot image profile found for platform x86 so a new image will be created. Calculating hashes for requested content. Changes have been made, boot image will be updated. Windows PE WIM E:\Deploy\Operating Systems\Windows 7 x86 Enterprise\Sources\boot.wim will be used. WIM file mounted. Set Windows PE system root. Set Windows PE scratch space. Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Error: 8 An error occurred. DISM could not be initialized in the local folder. Ensure that DISM is installed correctly and that all of the binaries are present. Exit code = 8 DISM /Add-Package failed for component C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\, rc = 8. Added component winpe-hta Deployment Image Servicing and Management tool Version: 6.1.7600.16385 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. Exit code = 3 DISM /Add-Package failed for component C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\en-us\, rc = 3. Added component winpe-scripting Some Ideas? Thanks in advance.
  8. Hi Friends, Me again, now I need deploy two operating systems in dual boot with MDT 2010, but the unattend instalation process fails. the system shows me wich operating system I want to deploy but does not apply the other partitions. this is my unattend. somebody catch what is wrong? The Idea is: Windows XP in C partition User Data shared in D partition Windows Vista in E partition Deployed with Server 2008 R2 x64 thanks a Lot in advance. Best Regards
  9. Hey peeps, can you please read this: then re-read attentively: and then convince yourselves that although the MS guys used a set of very confusing terms: the "master boot code for hard disk partitions" is the CODE in the bootsector or PBR and NOT the MBR (which bootsect.exe won't even touch) The MBR is the Master Boot Record and it is accessible through the \\.\PhysicalDriveN kind of object ONLY. The PBR is the partition bootrecord and it is accessible through a drive letter (LogicalDrive). The normal MBR does NOT contain code invoking ANY loader, it simply loads first sector (the PBR or bootsector) of the active partition found in it's partition table. The PBR or bootsector contains code invoking a loader like NTLDR or BOOTMGR. Bootsect.exe only changes the code in the PBR or bootsector of the partition addrtessed by a volume letter. jaclaz Hi good day. well yesterday I made some test with the commands that suggest me, but in all commands I recieve the same message "access Deny" with the same result executing the command from my virtual drive than ramdrive, what could be wrong in my boot image?
  10. Hi, I use Total Commander is a Portable aplication, just copy the content of the folder in system32 and that´s is all, Note: you need have XML suppot Installed on WINpe
  11. I fear that if, I used the command bootsect.exe /NT60 ALL /Force, the comand replace successfull the mbr but when i try to start Windows still have the message. "bootmgr missing"
  12. ho, that´s because bitlocker and safeboot I use to encript the machines and as you know this aplications replaces the mbr for another one, i suppose that´s the reason of my issue.
  13. Thanks in other test if i call this command from X:\windows\system32 a popup appears with the legend Bootrec is not a valid win32 application another suggest?
  14. Hi everyone, Now my deploy servers needs support 3 diferentes enviroments I need apply Windows XP, Vista and Seven from the same server, I resolved this issue with differents boot.wim for each operating system. but i have another problem, with this mixed enviroment the MBR starts to being a nightmare, I try call the command "bootrec.exe /fixmbr" from my Z: drive after the image applies but i recived the message "Acces Denied" instead of repair the mbr. in other test if i call this command from X:\windows\system32 a popup appears with the legend Bootrec is not a valid win32 application. to be clear, I copied this file in the hard way to my Z: drive, where my Z drive is my share folder in my server. So, How i can repair the mbr of each machine automatically after each image aplication? All this over Windows 2003 and Winpe 2.0 Again. Thanks in Advance.
  15. Ok wait. the loading screen of begin isn´t related with the source folder. is relates to boot manager. make this execise if you replace de bootloader of Win 7 with one of Windows vista the windows logo loading screen changes from Win 7 to windows vista.