[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


HP Homeserver, domains, and trusts

Posted on 2009-04-24
Medium Priority
Last Modified: 2013-12-04
I need some help with overcomming this problem.

I had created a Windows 2003 domain server and joined my Homeserver to it. The domain server was setup in a virtual machine stored on the homeserver. I had it running fine and it was running off of the homeserver itself. I also added my computer to the domain. With the security policies, I set it up to only allow access from the network and terminal services to the Domain Admins group (bad mistake). I always leave my homeserver on too, so the vm machine would always stay on as well. The shares on the homeserver were setup to be allowed to my domain account and the domain admins.

Problem came when I walked in today and found it inexplicably off. I luckily can login to my computer. Problem is... I cant login to my homeserver. As you can see, I cant remote into it cause the login's are denied access. I cant access the vm to start it up because it's only avail to the domain accounts, and since domain server is offline, cant logon. I cant access the homeserver locally, cause as we know, it doesnt have a display (I was looking into the usb adaptor > VGA, but I dont know if it would install).

So, there's my problem. I dont believe u can take out the harddrives and plug them in individually and take the info off them. I tried creating a replica domain vm server, but doesnt work because of the trust issues. I dont know where to begin with it.
Question by:helloandhiz
  • 2

Accepted Solution

cpottercpotter earned 2000 total points
ID: 24231478
Should be able to extract VM from Home Server and fire up on another machine to get your domain controller back. Use a bartpe or similar boot disk, or slave the drive in the second machine to get the virtual machine.

Author Comment

ID: 24232669
I figured out why it shut down... seems that since Windows Home Server is considered Windows 2003 Small Business server, it doesnt have licensing to be joined to a domain and will shutdown after 60 minutes of being attached to a domain for migration purposes. Time to do some experimenting it seems.

Expert Comment

ID: 24233089
Yes also limited to 10 client connections to the home server.

Expert Comment

ID: 24439732
Check out these links (and the rest of the website)

I would advice to put AD on the WHS itself, not on a seperate VM.
That way your WHS aka SBS is your primairy DC and you are not in trouble of the EULA.

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Active Directory can easily get cluttered with unused service, user and computer accounts. In this article, I will show you the way I like to implement ADCleanup..
Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units? This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses

873 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question