Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Br4tt3

  • Rank
    World famous sausage eater...
  • Birthday 10/13/1975

Contact Methods

  • MSN
  1. Deploy Linux from within WinPE / WDS?

    Awsome, thanks, this is prolly what I am looking for.... already got it up and running! And for the suggestion with running it in mixed mode (WDS), it does NOT exist in 2008, only on 2003 I think...
  2. Hi folks, So, I am a total n00b @ linux and how it works, but there are people at work that will help me out in that department... my problem is, we are running RIS/WDS on 2003 as our PXE solution. From RIS we are able to boot and deploy Linux just fine, however, as we will migrate to 2008 on the Windows side, WDS will be running in native mode! So, when running Windows 2008 WDS in native mode, how do u use WDS as the single point of PXE booting for deploying Linux operating systems? I have tried searching for the info, and everything points back to RIS and NOT WDS!!! I really hope that MS haven't put us into the corner with this "enterprise" solution, and that we need to segment our networks so we need multiple PXE sources.... I guess we are not the only ones that want one PXE deployment point for all of the platforms.... Does anyone had some expierence with deploying Linux from within WinPE 2.0 / WDS (native mode) or know where to find some information on how to solve it? Looking forward to any pointers or help from the forum! Thanks in advance...
  3. Hi, If this seems to be related to network issues / performance on networking, then I have had the following problem (even though it is a mixture of OS and HW / drivers). On many of our servers which were working greate with 2003 (as u mention) we saw a decrease in performance over network performance once we got 2008 up and running (x64 Enteprise as well). Finally, it was resolved by disabling SNP (Scalable Network Package) that is default enabled from 2003 SP2 and forward. SNP can be disabled trough the registry or in some case turned of from BIOS (most often TOE) or the driver package that u r running. Otherwise, my history tells me, when really wiered stuff is happening, check the drivers and try updating them.... needle in a haystack but anyway Might be it.... u never know.
  4. According to me, i dont think that there is a way of disabling the checkbox unless u do it from the unattend file which I thought I would like to do, however: 1. Please consider that disabling IPv6 on 2008 might lead to odd behavioud with different services that you might run on top of the operating system which requires IPv6, for example FailOver Clustering which requires the presence of IPv6 or it will not work. In the same time, I dont want users to see that they have an IPv6 address displayed on their boxes when we dont use + WMI reports back IPv6 setting (when enabled) which messes up our audit settings, to solve it I used the registry that u mentioned, that removed it from the ipconfig /all command, fixes our audit + but still present us with the possibility to install clusters and so on.
  5. For example: If u wanna do it from batch, then have a .cmd file executing the servermanagercmd.exe file with some parameters, pointing onto an .xml file which contains the component name.... The xml would look something like this one... <ServerManagerConfiguration Action="Install" xmlns="http://schemas.microsoft.com/sdm/Windows/ServerManager/Configuration/2007/1"> <Feature Id="SNMP-Service" /> </ServerManagerConfiguration> Run either servermangercmd.exe or ocsetup.exe to install SNMP after Win2008 is installed... or by an unattend as described above. Good luck...
  6. Hi, I am almost sure that the suggested way is the only thing that you will be able to acchieve. It will not possible for example to run the hypervisor below an WinPE instance for example or something like that... The only logic thing that comes to mind are dumping excessive binaries, hacking and modding the OS so that it does NOT make usage of diffrent native components... The easiest thing to solve it trough is of course running Windows 2008 Core edition that will do the trick for u...
  7. Hi, Start, cmd.exe (as admin): then type <net time /?> - i am guessing for the <net time /SETSNTP> option....
  8. In Windows 2008 FailOver Cluster services, once needs to generate a Cluster validation report before MS will support and answer your questions in case of problems! Anyone know how to generate it / launch it by script etc?
  9. Hi pepz, Today, we are running alot of SAN booted server (no local drives) over Fibre Channel / HBA. This is NOT a problem and is working smoothly with WinPE 2.0 and 2008. However, my storage guys are now stating that are going to have iSCSI devices that we need to be able to boot against. So, here it goes: Anyone had any expierence with it and what to share some light on this chapter? I dont understand how Windows will be able to see a NIC(iSCSI enabled) as way for a reading / writing data to / from! Thanks for any advice on how to move along....
  10. runonce with waik

    Hi, In XP/2003, the unattend setting [GuiRunOnce] has been replaced by the RunSynchronous section of the unattend.xml file in Longhorn versions. Just map it into ur correct phase and u should be good to go. Another thing, saw ur country flag in the left side and there is a MS KB that relates to hebrew entries specific to RunSynchronous. http://support.microsoft.com/kb/931824 Keep trucking....
  11. Running ImageX from VBScript

    Hi, First of all, like u say... if u try to run notepad.exe it works right? well, as long as u execute ur .vbs file with cscript.exe (default is wscript.exe) from within an existing cmd console, this should also work.... if u try to execute a CLI command from an vbscript which in turn is kicked by wscript.exe, there should only be quick flicker on the screen... instead, open up cmd.exe, type <cscript.exe my_vbs_file.vbs>, execute and u should see the /INFO list poping up.... Option Explicit WScript.Echo ExecAppRM("imagex.exe /info D:\Distribution\Captures\WINVISTA_X64_ENT.wim") Function ExecAppRM(pstrCommand) Dim oRun Dim n Dim WshShell Dim strResult Set WshShell = WScript.CreateObject("WScript.Shell") n=0 Set oRun=WshShell.Exec(pstrCommand) ExecAppRM = oRun.StdOut.ReadAll End Function Hope it does it for you....
  12. Dual boot XP and Vista

    Hi, Well, first off, use a file based image tool (such as imagex.exe) and NOT sector based imaging tools like ghost.exe. Secondly, the command that you to fiddle around with to get the multiboot option to work between XP and Vista is bcdedit.exe on the Vista box. Once Vista is installed on one of your machines, you will have to run a command from bcdedit.exe to indicate to the bootloader where to run a second boot option from, hence the XP installation. Sorry, I dont have the correct bcedit.exe command in place to get it working, but atleast that is what you wanna do.....
  13. Hi, I am also using the MDT (Microsoft Deployment Toolkit) as a build environment, which would create "generic" images.. Works just fine for me.... and free of charge! To answer your questions listed above (all of them are addressed within the MDT framework): Q1: PXE boot to WINPE... A1: It is also what MS is doing within MDT Q2: I Partition and format drive... A2: Check Q3: I Use ImageX to deploy a custom Image (I used the Sysprep /OOBE /Generalize /Shutdown switches and then created my image) A3: Exactly what MS are doing within MDT Q4: I Now I copy my PNP drivers to the drive (unattend.xml has the locations in it) A4: I personally use a vbscript for reading the registry key that is created if booted over WDS, to determine the location container for the driver package, and apply it using the imagex.exe commando, not from within the unattend.xml even if possible. The drivers can be injected with drvinst or Package Manager using CLI/WSH. MDT also has a MS solution for it even though I find it somewhat troubblesome. Q5: What do I do with the file? A5: The name of the file must be unattend.xml or autounattend.xml according to MS documentation or the panther (setup engine) engine will skipp the exection of it. The panther engine, searches a predefined number of directories to check wheather it contains an unattend.xml or autounattend.xml file. The diffrent directories, are also prioritized which are documented within the unattend.chm file that is accompinied with the WAIK tools (search for panther). Personally, I store mine in C:\Windows\Panther.... Q6: Does it get rename? A6: Not to my knowledge... Q7: Where does it go so when WInPE rebots and teh host boots up it is used and builds with those settings? A7: Once the sysprep phase has ended, the image is saved onto a network server. The image would then contain the actual files contained on the "base" machine (if not skipped by a .wim script) which MDT defaults to. Once you apply the image that you saved to the network location by for example WDS to the target machine, the panther engine would start to scan it's predefined order of directories. In my case, it would search for example the root of C:, not finding any unattend.xml file until it hits c:\Windows\Panther. Now, the setup engine would determine, if the .xml is properly formated (xml) and if it contains all the required params. We assume it does.... Q8: I assume it has to be placed somewhere on the host's hard drive. But where? I can't find this information anywhere. A8: Listed above... however, the .chm files contained within the WAIK tools (search tag "panther" / "setup phase") should prolly provide you with the start documentation for getting on with it... I strongly recommend the MDT as it can be highly customized for your deployment, and get you on the way pretty fast... Hope it helps and gg!
  14. On the limitations on the bandwidth; the answer is QoS (Quality Of Service) which exists within networking devices for example.
  15. Running tests within WinPE 2.1

    They support adding drivers for Gfx, Masstorage devices (SATA/HBA/SCSI/IDE), NIC... Sound and graphics are somewhat challenging as they often use additional .dll / .exe and so on which are NOT often mapped to conent of a WinPE image. Yes, ActiveX is NOT part of WinPE.... defeats the purpose really.