Jump to content


xbliss

Established Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About xbliss

  • Rank
    Member
  1. SBS Windows Server 2008 Domain Controller: Unable to re assign DC DNS IP from 3rd PCIe NIC to 1 of 2 MoBo NICs on Dual LAN Dell Server **Issue:** I've been unable to take the x.2 IP (for DNS & DC) currently assigned to PCIe NIC and assign it to one of the MoBo NICs. What would be foolproof steps to do so? ---------- SBS Windows Server 2008 Domain Controller: DC IP assignment issues on Multi NIC Dell Server **Hardware:** - Dell T410 Server – Dual NIC + Additional NIC added by tech **History:** - For some weird reason an MSP tech as well as Dell tech concluded initially that the MoBo was gone. Then they concluded that the NICs were busted. - I asked them (on the phone) to check via a Bootable PE/ Linux Disc and the NICs showed but they said not working. - They chose to install 3<sup>rd</sup> a PCIe Gigabit NIC and IP was assigned and things got working. - Apparently, in their & my experience when forced to, the Mobo NIC takes up the 169.x.x.x address **Additional:** - There’s a **temporary DC** (**Win Server 2008**) instance sitting on a Win 8.1 PC Box on Hyper V (**192.168.10.201**) - Also, realized there's some FSMO role issues between both DCs. **The MSP guy had tried to transfer FSMO roles to the temporary Win 2008 DC, but from my recent reading, SBS DCs are not really fond of such things.** - **From my CMD output a month back it seems the FSMO roles were partially divided between both. Weird?** - **DHCP function** disabled and managed by a **Router/ Firewall** (at the moment) (**192.168.10.6**) **Recent:** Fast forward a few months, I realized the NICs are working (as I booted the machine via another HDD into a different Win Server 08 instance). Also visible & working via Dell OMSA bootable Discs (based on Linux) - I tried reassigning the IP to the original MoBo NICs but it just wouldn’t hold. - I could get the MoBo NIC to take other IP addresses (.x.3/.x.4), but it would not be able to take the DC IP, even if I remove the (.x.2) IP from the 3<sup>rd</sup> PCIe NIC. - MoBo NIC is also able to get different IP via DHCP (hence DHCP is shows enabled below) - Things are functional/ working but I'd like to eliminate this PCIe NIC prior to a P2V - Also, would like to understand why and how this issue has come up? - I thought it should be as simple as um-assigning IP from PCIe NIC and then assigning it to 1 of the two MoBo NICs - **Are there Fool proof, kosher steps to do that?** Upon googling I learnt **there are some DNS/ DC/ NIC assignment dynamics** – But **nothing clear & conclusive on how it works, how to fix and get around this**. Thoughts, suggestions, direction and solutions on how to fix this ? **Admin CMD: `ipconfig /all` Dump** <CODE> **Windows IP Configuration** Host Name . . . . . . . . . . . . : OrgnztnSBS Primary Dns Suffix . . . . . . . : Orgnztn.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : Orgnztn.local **Ethernet adapter Local Area Connection 7:** Connection-specific DNS Suffix . : Description . . . . . . . . . . . : **Realtek PCIe GBE Family Controller** Physical Address. . . . . . . . . : 00-00-EF-3A-00-00 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::d0e9:c802:5f4a:beca%18(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.10.2(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 **Default Gateway . . . . . . . . . : 192.168.10.6** DHCPv6 IAID . . . . . . . . . . . : 436207855 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-72-81-8F-78-2B-CB-06-E3-CC **DNS Servers . . . . . . . . . . . : 192.168.10.2 | 192.168.10.201** NetBIOS over Tcpip. . . . . . . . : Enabled **Ethernet adapter LAN:** Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : **Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client)** Physical Address. . . . . . . . . : 78-2B-CB-06-E3-CC **DHCP Enabled. . . . . . . . . . . : Yes** Autoconfiguration Enabled . . . . : Yes **Ethernet adapter Local Area Connection 2:** Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : **Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) #2** Physical Address. . . . . . . . . : 78-2B-CB-06-E3-CB DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes </CODE>
  2. To Deploy a VHD to all domain PCs/ Laptops and set up for Native Boot? Not sure if this will do better as a Discussion or Q&A (mods feel free to switch), but I need answers for the 4 parts. Win 2008 Domain, Mix of Win XP, 7, 8 Machines. Prefer Free/ Gratis ways or Trial/ Freemium also works. I have PDQ Deploy Free but not sure if it can help? Will Spiceworks or LANSweeper help or something else? Dont have SCCM or time to set it up. Have downloaded MDT but not started using it as yet. In General - Prerequisite Task?? : Part 1: - Terminal Services/ Remote Services are not enabled - How can I enable them for access across the Domain so that I can log in as Domain\Admin for some night time tasks & cleanup activity? - And later Disable this to prevent misuse? Specific Task - 2 parts: Part 2: - One of these tasks is to drop a VHD (Mostly 7/8/10 based) to the C or D or E drive of the Machine, Set it up for Native Boot and run it to execute some stuff - Since most machines are GigE and dont have USB 3 I'd prefer to Broadcast/ Multicast/ Copy over the network - Preferably driven from Domain\Administrator side. Is there some smart way/ tool of doing this? Or do I have remotely log into each and create a shared folder/ drive to drop the VHD or broadcast/ multi cast it? Part 3: - When I do this for my own machine it's simpler: Either using BCDBOOT.EXE or EasyBCD at times. - I've also found some Powershell/ BAT script commands to invoke and call BCDBOOT to create the boot entry. But this is usually TUNED to a SPECIFIC PATH on my machine. In person task (maybe possible to minimize in Person by configuring some remote stuff) Part 4: PS: I'd prefer to do most part of this from MY MACHINE, except for the EVENTUAL NATIVE BOOT for which I will have to be there in PERSON (Unavoidable at Booting??). Or Maybe I can make the Boot entry default to the VHD, and ensure/ configure VHD such that the VHD has some "Remote Access" from my machine/ Admin? Thoughts/ suggestions on how I can do the various parts of the process (as much as possible from my desk).
  3. Thanks you. Been going through all that for a while. I have completed through these phases of the project. Using this context, please help me with this further at this location: http://www.windows-noob.com/forums/index.php?/topic/12735-what-is-significance-of-msr-sys-efi-partitions-for-win-81-native-boot-vhd-how/ PS: Why VHD Native Boot? So that moving my OS is a simple file copy/ transfer away from now. Allows me to plop it from SPro 3 to a bigger machine when needed.
  4. What is Significance of MSR, SYS, EFI partitions for Win 8.1 Native Boot VHD? How? I ask because I've built and native booted several variations of Win 8.1 VHDs on target SPro 3. I'd like to know pros & cons. CONTEXT: So, with a lot of help and input from multiple amazing people from multiple forums and coming closer to the goal of my project. I have found and tested the ways and means to complete the steps in my project. Some interesting questions and thoughts have come up. (http://forums.mydigitallifeSPAM&#33;/threads/62362-Virtualize-Win8-1-BIOS-MBR-Physical-Partition-gt-to-gt-WIM-Image-gt-to-gt-UEFI-GPT-VHD?p=1085352&viewfull=1#post1085352) PROJECT MILESTONES SO FAR: A - Was able to find articles that help bypassing Sysprep errors on Win 8.1 Did some extensive Driver Cleaning/ Reseting from OEM/Intel/Non MS drivers to MS Win 8.1 native drivers e.g. Prototype sample runs involved Sysprepping Fresh Win 8.1 installs while eliminating issue causing Metro App packages. B - Played with DISM, Disk2VHD, GPTGEN in various configurations with Win 8.1 e.g. Prototype sample runs involved imaging Fresh Win 8.1 MBR/ BIOS installs and converting or applying them to GPT/UEFI VHDs and native booting them in Step C C - Have been able to Native boot Win 8.1 VHDs using BCDBOOT: QUESTIONS & DECISIONS about MSR, SYS, EFI Partitions on Win 8.1 Native Boot VHD: I am left with some final decisions to make and questions.. Before I apply my Customized_Windows.WIM... What kind of Partitioning structure should I CREATE IN/ FOR my FINAL VHD? I ask because I've built and native booted several variations of Win 8.1 VHDs on target SPro 3. Some with Single Partition Volumes and others with Sys+EFI etc. OPTIONS/ EXAMPLES of Sample VHDs executed & installed on Surface Pro 3: [:\Windows] DISM Installed Natively [sys:300M][EFI:100M][:\Windows] Vanilla Install via Hyper V Possibly also doable using VDisk commands via Native Install as well. I guess. Also, during this Vanilla install it was trying to create the MSR partition in addition to the above. I did read about the MSR, SYS, EFI partitions online as well as how OSes can also run without those. https://technet.microsoft.com/en-us/library/dd799232(v=ws.10).aspx https://technet.microsoft.com/en-us/library/dd744301(v=ws.10).aspx Also, if ever V2P for Upgrading to Win10 and then P2V again There were some workarounds posted on Technet (need to find link, will find and post) as Windows cant upgrade on Native Boot VHD. BOOT BCDBOOT QUESTION: With single partition volume VHDs, its simple & clear how to APPLY and USE ..BCDBOOT. With these SPECIAL PARTITIONS, I am curious what would the best way to "direct" BCDBOOT > > > ?? From where to where? https://technet.microsoft.com/en-us/library/hh824874.aspx https://technet.microsoft.com/en-us/library/gg577238.aspx EXISTING HARDWARE PARTITION VOLUMES: SPro 3 HDD (UEFI Only): [sys:350M][EFI:200M][:\Windows][Recovery:5GB] X61T HDD (BIOS Only): [:\Windows]
  5. Ok Guru sir I made a fresh post to CLEAR OUT some of the matter. I hope this can bypass the whole MBR > GPT conversion drama? http://www.windows-noob.com/forums/index.php?/topic/12699-virtualize-win81-bios-mbr-physical-partition-to-wim-image-to-uefi-gpt-vhd/
  6. Virtualize Win8.1: BIOS + MBR Physical Partition > to > WIM Image > to > UEFI GPT VHD Virtualizing Win8.1 from BIOS + MBR Physical Partition > to > .WIM Image > to > UEFI GPT .VHD Sometime last year I found out about Native boot VHDs and tried to go that way for good. There were some issues with hardware and OS (Win7 at the time) not working out and lot of new things that I was learning about VHDs. Anyways, that confusion, learning and failure led to a better path So this 2015, I figured out how to get VHDs (with Fresh Win 8.1 Installs via Install.WIM DISM Apply Image) to Native Boot on Surface Pro 3 (Sp3). I am going to attempt doing the following steps using DISM/ ImageX: MBR [Customized Win 8.1] (Physical) > Create Image > [Customized Win 8.1 .WIM] (Virtual - File based so - No sectors or MBR/GPT?? ). [Customized Win 8.1 .WIM] (Virtual) > Apply Image > [Empty New GPT .VHD] (on SP3) My thought is that by going to .WIM I bypass the whole converstion drama between MBR/BIOS & GPT/UEFI as the .WIM is agnostic of both of them? Is this a valid thought or not? Thoughts? NOTE: I can.. try out the above with creating a small FRESH MBR Windows 8.1 partition on X61T/ T61 and then doing the above 2 steps. Convert it to a .WIM and then applying to a GPT .VHD I am guessing a SYSPREP is recommended somewhere in between. Someone somewhere also mentioned doing Sysprep in a VM/ Hyper V instead? Thoughts? Where and how would you recommend applying the SYSPREP?
  7. Please do respond to the posts I made after your reply In short: I figured out how to get VHDs (with Fresh Win 8.1 Installs via Install.WIM Apply Image) to Native Boot on Sp3. I am going to attempt doing the following: MBR [Customized Win 8.1] (Physical) > Create Image > [Customized Win 8.1 .WIM] (Virtual - File based so - No sectors or MBR/GPT?? ). [Customized Win 8.1 .WIM] (Virtual) > Apply Image > [Empty New GPT .VHD] (on SP3)
  8. I've been reading that article since last year Ha ha! many more like them.. But I did not get to connect with a Guru such as your self. Anyways, there's some positive news. For some reason the previous GPT/ UEFI VHDs I had created were messing up with SP3 native boot. Add to that the Bitlocker drama that SP3 has inherent, caused additional trouble. So, I UNDID all of SP3's Bitlocker drama. After that, I created a few more "Brand New VHDs" on SP3 in various different ways that I could find on the web. Some with GUI/ DiskMgmt some with DiskPartition Vdisk commands and so on. (I will try and post the ones that really worked). After a lot of experimentation, I found that I was missing 1/2 small things and finally got a "Fresh Win 8.1" to Native Boot on the Sp3.. Yaay! (PS: Which Driver Package/ Files should I use for this? The June download has bunch of different Files: Zip, MSI etc. Of course, now I know its possible via DISM I just need to rinse repeat this 1/2 more times to be sure ANYWAYS, since I am in a timezone thats 12 hours away from the US right now, I am hoping that by the time I wake up I will have WISDOM from you for the next step: I have specific Physical OS in Single partition (MBR/BIOS) with bunch of Specialized Apps and Configurations/ Settings that are not easily to replicate. Previously, I have used Sysprep/ OOBE and Disk2VHD to pull this into a VM (Hyper V/ VMWare). 1. Now, this is the key question.. Given that VHDs can be MBR or GPT.. But, .WIMs are not MBR or GPT.. right, they are file based. Not sector based. I am wondering if instead of pulling this into a VHD (like I did with Disk2VHD), I can somehow pull this into a .WIM using DISM or MDT (without Drivers/ Hardware Profile)? 2. If I can do that, then I could use that Special WIM (which is free from MBR/ GPT) drama and APPLY it to a BLANK GPT VHD that works/ is present on the SP3 ? Are these steps valid? That way I dont have to do a MBR > GPT conversion of the VHD and try to get it all to boot? Thoughts? If its possible.. then please let me know what kind of DISM command-line / shell stuff or MDT stuff would I have to use for STEPS 1 & 2. Thanks in advance and I really appreciate all your help.
  9. PS: Made sense to create new thread.. You site and forum is amazing and I wonder why it did not show up on my Google searches regarding issues for Surface Pro 3. I will link to that thread here. I figured the MDT might be easier than SCCM for me.. But maybe you have a simpler way for this simple task. Create/ Image/ Sysprep Win 8.1 & Win 10 VHDs WIMs for Native Boot on Surface Pro 3 for isolated activities without huge server setup?
  10. Create/ Image/ Sysprep Win 8.1 & Win 10 VHDs WIMs for Native Boot on Surface Pro 3 for isolated activities without huge server setup? Previously what I have done: So, I have a bunch of Win 8/8.1 VHDs/ WIMs that I guess I can Sysprep natively or Sysprep/ Hardware/ Clean out in a VM. These are setup with lots of applications and settings that I can't and do not wish to replicate from scratch. Normally, its as simple as dropping these Sysprepped VHDs onto a machine, then booting, installing drivers manually. Before I drop VHDs to a new machine, I just test "Fresh" Win 8.1 VHDs on them (Created with Simple XImage/ DISM > apply image from fresh Install source) to see how the fresh Installs workout on new hardware and update their drivers before I try that with my Special VHDs. Then BCDBOOT steps and get it to boot and then install my drivers. Even VHDs <> WIMs seemed relatively simple. Equipment Etc I have Win 8.1, DISM, just downloaded MDT (not usage experience) and can get the ADK etc that I am seeing on the forums. Without have an extensive SCCM or PXE/ Deployment Server setup etc. I'd like to do the following.. Note: I do have an ancient Synology CS407 and there is some material out there on putting PXE Server on top, but I want Native boot VHDs, not to wipe out the existing SP3 disk structure. Story So far with Surface Pro 3: Lack of simple instructions on how to setup VHDs or convert Sysprepped WIM images to VHDs that can native boot on an Surface Pro 3 I am guessing with your expertise it might be served the right steps. I realized thanks to this link by Thurrot that SPro 3 has extensive lock down and default Bitlocker. https://www.thurrott.com/mobile/microsoft-surface/2515/how-to-dual-boot-windows-10-on-surface-pro-3 So, I just disabled Bitlocker on the C:\ and the Fresh Win 8 VHD I created. Disabled Secure Boot. Havent disabled TPM as yet. Does something else/ something special need to be done to Create & Native Boot VHDs on Surface Pro3? (Drivers??) I did notice the videos and downloaded some of the Deployment Guides for Surface Pro 3 but they are extensive and needed for large number of devices. https://technet.microsoft.com/en-us/windows/dn903161 I am just starting to play with the Surface Pro 3 and being able to experiment and native boot on 'separate' .VHDs/.VHDXs would be great. Please guide me on what needs to be done additionally/ differently as compared to the simple (ImageX or DISM) steps outlined above. Does the VHD or WIM image needs to be injected with SPro3 Drivers? Is that it, then please point me to a How To or steps to do so? So far, all I get are black screens (frozen/ hung native boot) or red screens (disabled Secure Boot) or frozen screens when I try to boot from the Fresh VHDs. Thoughts and advise please?
  11. PS: Made sense to create new thread.. You site and forum is amazing and I wonder why it did not show up on my Google searches regarding issues for Surface Pro 3. I will link to that thread here. I figured the MDT might be easier than SCCM for me.. But maybe you have a simpler way for this simple task. Create/ Image/ Sysprep Win 8.1 & Win 10 VHDs WIMs for Native Boot on Surface Pro 3 for isolated activities without huge server setup?
×
×
  • Create New...