I've been handed an old Win2000 IAS server that I need to move to another
server since its on almost 6 year old hardware!  Is there a way to migrate
it easily or do I need to simply install IAS on a new Win2000 server and
recreate each RAP manually.  The kicker is that we use EAP for SmartCard
authentication against a non enterprise Win2000 CA.  Any help is appreciated
since this is new to me.  Thanks!

[ Post a follow-up to this message ]

"Mike B." <Autobahn97@hotmail.com> wrote in
news:OX4POyihEHA.712@tk2msftngp13.phx.gbl:

> I've been handed an old Win2000 IAS server that I need to move to
> another server since its on almost 6 year old hardware!  Is there a
> way to migrate it easily or do I need to simply install IAS on a new
> Win2000 server and recreate each RAP manually.  The kicker is that we
> use EAP for SmartCard authentication against a non enterprise Win2000
> CA.  Any help is appreciated since this is new to me.  Thanks!
>
>
>

Probably the easiest approach is to install W2K on the new hardware, then
install IAS.

On the old server export the IAS configuration to a file using netsh
commands.

Copy the file to the new server and use netsh commands to import the IAS
configuration.

From the IAS Help:



To copy the IAS configuration to another server:

At a command prompt, type netsh aaaa show config <path>\file.txt. This
stores the configuration settings, including registry settings, in a text
file. The path can be relative, absolute, or a UNC path.

Copy the file you created to the destination computer, and at a command
prompt on the destination computer, type netsh exec <path>\file.txt. A
message appears indicating whether the update was successful.


Notes

You do not need to stop IAS on the destination computer to run the netsh
exec command. When the command is run, IAS is automatically refreshed with
the updated configuration settings.

This procedure will not work if the source and destination computer are
running different versions of Windows 2000.

This procedure replicates all IAS, remote access policy, registry, and
logging configuration.



--
James McIllece, Microsoft

Please do not send email directly to this alias.  This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

[ Post a follow-up to this message ]

Awesome info James, I wanted to add that you will also need to export the
certificate of the server and import it again on the IAS server. If the
certificate is allowed to be exported. Otherwise, you will need to request a
new certificate. (The server name should match the server name of the old
IAS server, so you will need to take the first one off line, join the new
one to the domain and then import the certificate)


--
 ========================================
=====
This posting is provided "AS IS" with no warranties, and confers no
rights.
 ========================================
=====

"James McIllece [MS]" <jamesmci@online.microsoft.com> wrote in message
 news:Xns954E76D3E7954jamesmcionlinemicro
s@207.46.248.16...
> "Mike B." <Autobahn97@hotmail.com> wrote in
> news:OX4POyihEHA.712@tk2msftngp13.phx.gbl:
> 
>
> Probably the easiest approach is to install W2K on the new hardware, then
> install IAS.
>
> On the old server export the IAS configuration to a file using netsh
> commands.
>
> Copy the file to the new server and use netsh commands to import the IAS
> configuration.
>
> From the IAS Help:
>
>
>
> To copy the IAS configuration to another server:
>
> At a command prompt, type netsh aaaa show config <path>\file.txt. This
> stores the configuration settings, including registry settings, in a text
> file. The path can be relative, absolute, or a UNC path.
>
> Copy the file you created to the destination computer, and at a command
> prompt on the destination computer, type netsh exec <path>\file.txt. A
> message appears indicating whether the update was successful.
>
>
> Notes
>
> You do not need to stop IAS on the destination computer to run the netsh
> exec command. When the command is run, IAS is automatically refreshed with
> the updated configuration settings.
>
> This procedure will not work if the source and destination computer are
> running different versions of Windows 2000.
>
> This procedure replicates all IAS, remote access policy, registry, and
> logging configuration.
>
>
>
> --
> James McIllece, Microsoft
>
> Please do not send email directly to this alias.  This is my online
> account
> name for newsgroup participation only.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

[ Post a follow-up to this message ]