There are two ways about domain controller, 
Active Directory Federation Service and Windows Azure Connect, perhaps.

I will read below about  Windows Azure Connect .
But now I do not have ideas at all, sorry.
http://msdn.microsoft.com/en-us/library/gg433016.aspx
http://msdn.microsoft.com/en-us/library/gg454720.aspx
http://social.msdn.microsoft.com/Forums/en-US/windowsazureconnectivity/thread/fc858c4f-1e0f-4ea7-8276-d596ba3a5f06
http://blogs.msdn.com/b/windows_azure_connect_team_blog/archive/2010/12/10/domain-joining-windows-azure-roles.aspx
http://engineermemo.wordpress.com/2011/01/12/vm-role-%E3%82%92-active-directory-%E3%83%89%E3%83%A1%E3%82%A4%E3%83%B3%E3%81%AB%E5%8F%82%E5%8A%A0/

Shinichiro Abe

On 2011/05/11, at 9:22, Karl Wright wrote:

> I seem to recall that Azure is available for free though MSDN, which
> means it is likely to be affordable.  Can you find out more details?
> How do you go about setting up a semi-permanent instance of (say) a
> domain controller?
> 
> Karl
> 
> On Tue, May 10, 2011 at 8:07 PM, Shinichiro Abe
> <[email protected]> wrote:
>> What about Windows Azure?
>> It seems that it can deploy MS products and use java,
>> I do not know the details though.
>> Isn't it relevant?
>> 
>> Regards,
>> Shinichiro Abe
>> 
>> On 2011/05/10, at 20:08, Karl Wright wrote:
>> 
>>> I've pretty much given up on getting access to the testing
>>> infrastructure I originally built for ManifoldCF that is now owned by
>>> qBase.  I was wondering if anyone had time or energy to research what
>>> it would take to build such an infrastructure using Amazon cloud
>>> servers.  Basically, we'd need at least one active directory domain
>>> controller instance for each configuration (LM, NTLMv1, NTLMv2 NTLM2
>>> session), and a repository server per domain (or more, depending on
>>> whether we can get some of these repositories to coexist with each
>>> other).  I would start with a SharePoint instance and CIFS share on
>>> each such server, and we can grow from there.
>>> 
>>> What we'll also need is some kind of allocation mechanism so that
>>> anybody can run tests anywhere, provided they have internet access,
>>> and not collide with *other* people running tests.  Any ideas?
>>> 
>>> Karl
>> 
>> 

Reply via email to