Install configure ris server 2003

If you are going to accept the challenge of installing and configuring the RIS service on a Windows Server then you need a plan. Think of this page as a mini-site map for RIS. Even if you have successfully installed RIS, there is still a deal of configuration surprises at the Active Directory Users and Computers.

Be prepared. It wont let me log on as anyone else other that Admin on the member server as it currently has no roles. Office Office Exchange Server.

Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. You can then deploy the image to other machines through RIS. The nice thing about deploying an image rather than relying on Setup files is that your image file can contain more than just the Windows operating system. You could, for example, install Microsoft Office and your antivirus software onto the workstation prior to building the image file.

This would allow those applications to be deployed along with the operating system. You will just have to verify any time you perform a deployment that you have enough licenses for Windows and for any applications that are being deployed. Setting up a RIS image and preparing for your first deployment can be a real pain. So why not just use an imaging utility such as Symantec's Ghost instead? The reason is the way that Windows makes use of SIDs.

When you install Windows, it creates a unique SID for the machine. If you use a utility like Ghost to duplicate a machine, you will also duplicate the machine's SIDs as well.

If you place two machines with common SIDs onto the same network, you will have some really strange access control problems. There are SID randomizer programs that can supposedly change all of the SIDs that exist on a machine, but Microsoft has indicated on more than one occasion that such utilities are "inadequate" and should not be used. I have never personally used such a utility, so I can't tell you if they really work or not. What else is new?

There are a couple of things. First, Windows 's implementation of RIS was less than secure. It had a nasty habit of transmitting passwords in clear text format, for example.

The problem was that there were a lot of cases in which this floppy disk just didn't work. In Windows Server , you can still create a RIS client boot floppy, but the floppy has been improved to make it compatible with more systems.

Some of the most important limitations that you need to know about involve the way that RIS works with hard disk space. RIS will only image a single partition. Therefore, when creating the client machine that you will image, you must make sure that only a single partition is used.

There are also disk partition requirements on the RIS Server. You can't store a RIS image on the boot partition or on the system partition. A couple of other limitations that you need to be aware of involve the RIS server. The server cannot be multihomed. A multihomed server is a server with multiple network cards. Logon to the Windows Server. RiPrep will copy another, more complete image of this client to the RIS server.

A final point, to configure RIS on the server, you need to select the computer object in Active Directory User and Computers, properties, then select the Remote Installation tab. My advice is to investigate Group Policies for RIS, decide on whether to allow the installer to choose setup options, or whether to make the setup silent with no screens and no choices. See here for a step-by-step RIS setup guide —.