crashnburn4u

Retain File Names without name mangling when Move/ Cut select Files from Recycle Bin to a selected location Retain File Names without name mangling when Move/ Cut select Files from Recycle Bin to a selected location Move/ Cut select Files from Recycle Bin to a selected location retaining File Names without name mangling? "Windows Behavior" when cutting/ pasting or drag-dropping the files to some location/ folder, all the names are mangled. Names are mangled like this: $REA9O58.xxx The only option Recycle Bin gives is: Restore (do not wish for files to go back and mixup with other files in Original Folder) or Cut (When pasted or Drag & Dropped to new location, the original name is mangled). Any way around this to put select files into other location folders from Recycle Bin? App/ Tool/ Hack/ Script/ PS??

https://superuser.com/questions/1217793/boot-win-8-1-partition-cloned-from-mbr-disk-to-empty-space-in-gpt-disk-with-exis Boot Win 8.1 Partition cloned from MBR disk to empty space in GPT Disk with existing Preinstalled Win 8.1 Partition? Boot Entry & Windows fix? I can easily press F12 at boot and choose between - Legacy BIOS Options and - UEFI Options - namely Windows Boot Manager - Probably points to the ESP FAT partition on HDD2 - GPT HDD & Partition layout as shown in Paragon HDM [![enter image description here][1]][1] - https://i.stack.imgur.com/5QyU2.png Now, I am cloning - W81_SP_CP2 (BIOS booting) - From HDD 1 - MBR - To - Unallocated Space - on HDD 2 - GPT HDD 2 already has OS_W81 (UEFI Booting) - Preinstalled Now, given "boot mechanisms" of Legacy CSM BIOS as well as UEFI, I believe there may be no way to boot the copy of W81 (.. Let me call it W81_BIOS) from HDD 2 until it becomes W81_EFI. **Is that true?** ---------- [![enter image description here][2]][2] - https://i.stack.imgur.com/9KY34.png PS - Paragon HDM does give me an option (Wizard UI link) to do/ convert/ add an EFI booting post cloning, but given its wording I am concerned/ wondering if it will "replace" / damange the existing entry for Preloaded OS_W81. ---------- I'd rather add a boot entry for W81_BIOS > EFI myself, using `BCDBOOT / BCDEDIT / EasyBCD or Easy UEFI` etc type of stuff in a known controlled manner rather than Paragon HDM doing something. I'm guessing this might be 2 steps: - EFI Boot Entry: How do I do that? Using bcdboot? or EasyUEFI/ BCD type of tool? Recommendation? - How I cloned it? (Using Paragon HDM > Copy Partition Wizard). Do I have to make any changes/ adjustments to the "cloned" Windows ? [1]: https://i.stack.imgur.com/5QyU2.png [2]: https://i.stack.imgur.com/9KY34.png

What if one was to use an older version and prevent this Auto Updating that was happening, which eventually led for it to stop working?

Can you please share the last release of where you got to on Win 8.1?

Do share such a valuable list with us all Maybe we can Git + Powershell it to make it semi automated

After Creating Hyper V External Switch: Setup and Assign Static IP Address for Host Machine? Lost Connectivity to Hyper V Host after Creating External Switch How to set static IP address on Window 8.1 Host with Hyper-V and Single network adapter Facing a similar situation but the answer posted is not enough to follow the steps and solve the issue outlined. How to Reassign Static IP to Win 8.1 Host that seems to have been lost in creating an External Virtual Switch in Hyper V? How & where in Windows 8.1 can one assign a Static IP to the Host Machine (with an External Virtual Switch)? It was easy to do so with the HV VM, but the static IP that was originally assigned on the Physical Host Adapter (NIC) (Before Switch creation) seems to be gone and cant use it to access Host via RDP anymore. Direction please? http://www.altaro.com/hyper-v/the-hyper-v-virtual-switch-explained-part-1/ Read this article and how HV changes Network Topology, but not sure, how and where in the Win 8.1 UI I need to assign the original Static IP to point and RDP towards the Host.

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^rd 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^rd 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>

Is it possible to change our User ID/ Login name/ Handle? (If available).

Never too late. It's still on a pending back burner.

My apologies jaclaz, for broken link, it was a copy past from SW, and I've not slept all night.

Unable to get Win 10 entitlement on Dell PCs COA sticker "Win 7 Pro OA India" I used an answer XML that didnt work too well and had to remove a few fields from it as WSIM would not validate those fields. Now this is the F up.. Not a single of my Genuine Dell machines has gotten activated. Used this method with fresh Win 10 1511 on an SSD.. https://community.spiceworks.com/topic/1620376-how-will-i-ever-get-my-machines-to-win10?page=1 Robert5205 May 20, 2016 at 12:43 AM Well, here's a tip. Stop doing it that way. Do it my way. I've upgraded 250 PCs in less than 2 months part-time. 1. Get an SSD. 2. Get a Win10 ISO. 3. Open PC. Connect SSD. 4. Do a full install of Win 10 to the SSD. Get your entitlement. 5. Reconnect original HD. 6. Repeat with next PC and Goto 3. [Edited to clarify that I re-use the SSD for each subsequent PC. Also, FYI, that you must do an install of W10, either in-place or clean, to get the entitlement. Simply booting to an existing install of W10 will not do it. This is the comprehensive thread where I tested every combination of upgrade/restore: https://community.spiceworks.com/top...-an-easier-way And this one shed some more light on this: https://community.spiceworks.com/top...er-key-regi.... ] Why is it not working? Their has COA sticker Win 7 Pro OA India. Do I need to use a different .ISO for this? I used the EN-US as most of my machines come from US, but this org I'm helping has these. . Is there a quick shortcut fix? Which "flavor" MSDN ISOs do I need to download?

Loving this thread. Will have to apply this stuff and then post back.

Windows 8.1 2 in 1 Tablet tied to unused Hotmail account whose password is forgotten? I have some old family folks who did not realize they created this, then they lent the machine to another old family member and now nobody remembers this password and this Outlook/ Hotmail account was never used by them. Apparently it was created by them when they went through the OOBE fresh machine process scenario. I am doing some major tech house cleaning for them. I doubt if we can do a reset via MS/ Hotmail and get a new password as we do not really have access to the Hotmail account as it was never used by anyone. Any other ideas on bypassing this, using some Boot CD to get through this?

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).