I am developer. Initially, at my client(employer) premises I had been given the company's desktop computer with Windows XP Pro SP3 joined to corporate Windows Active Directory domain (AD).
This is situation 1):
- 1) AD computer Windows workstation (or, for the sake of discussion, any Windows workstation operating system ).
Since, for developing, I needed full administration of machine and had rather limited in volume hard disk (of only 20 GB), while having the necessity to setup developing tools ((for ex., Vsial Studio 2008+2010) and servers (for ex., (MS SQL Server 2008 R2, SharePoint Server, etc.), I could not install another Windows. so I had to reformat the hard disk and install fresh
- 2) workgroup Windows XP Pro SP3 (i.e. Windows XP as part of workgroup, not joined to corporate Windows AD).
This resulted in complications to interoperate and develop, test, integrate against AD.
Suppose, I had a bigger hard drive, or for the sake of future similar situations, *what would have been more correct solution * in order to interoperate, communicate, develop + test + integrate with corporate AD while having full administration of developing machine (without access to corporate AD administration):
A) to install second (dual boot) workgroup Windows XP (for developing) leaving 1) for accessing AD resources + testing + integration, so having
- 3) dual-boot machine with 1) + 2)
B) to hack the single 1) Windows installation? to simulate/twist between necessities of isolation+full administration for developing+testing (i.e. having Windows as part of workgroup) vs. necessity of having Windows as part of AD?
Anyway, all setups (configurations), that I could imagine, have the disadvantage of separate booting either into AD machine Windows or into workgroup Windows machine (since it is impossible to have Windows to be both a part of workgroup and AD).
Dual-boot solution 3) also has disadvantage in duplication of quite time-consuming setup, configuration development environment.
Q1) What are the options of merging in one Windows the necessity of isolated development and accessing/development/testing in AD environment?
Q2) What are the differences in accessing both AD computers and workgroup computers under AD Windows local Administrator vs. under workgroup Windows administrator?
Sagar advised VirtualBox or VMWare player (which were lost in rantings).
Bart Silverstrim disadvised dual-boot and advised "look into virtualization (which is free in most cases). Snapshots and backups more handy, and you can simulate networks or multiple workstation configurations easily".
GregD again FAQed me though I again could not understand by which one of them. GregD wrote:
"You asked both of those questions yesterday and BOTH are currently at -1. So not only are you asking inscrutable questions, but you aren't interested in having them answered??"
Yes, Iam interested. What should I have understood from 0 answers and multiple downvotes?
Thanks once more to my ardent readers for close attention and closing this question! Though what was the point since it had been already marked as answered?
jscott just added an answer in similar subquestion
- http://serverfault.com/questions/170174/what-are-the-options-for-a-temporary-laptop-within-a-work-domain (What are the options for a temporary laptop within a work domain?):
"Could the laptop user just connect to his domain desktop via RDP?
He may access file shares on the domain desktop, from the non-domain laptop, provided he uses his domain credentials to connect."
Thanks jscott, once more, I love you!
Oooops, I formatted hard disk and re-installed everything from scratch (100 hours of work) and there was an answer how to convert domained Windows machine to non-domained one:
BTW, I reinstalled Windows with approval of company's high management. The problem was that sysadmins did not know how to install Windows in workgroup (they had the burned to CD images with all preset for local AD client setup).