RIS computers doesn't been created in the defined OU

I'm running a Windows 2003 server and I've installed RIS. I've copied
existing images to the new server. On the RIS-server I've type where I want
the computers to be placed. But when I RIS a computer the computerobject will
not be created in that OU, it will be created there the useraccount I used to
log on the RIS is. Please help me.

Thanks
.

Relevant Pages

  • RIS, same GUID, duplicates, Dell GX60s
    ... I'm deploying Windows XP by RIS from Windows 2000 SP4 servers. ... Most of the client computers are Dell Optiplex GX60's. ... workstation name from the RIS server as it thinks that it is the same machine. ... unique ID based on the MAC address. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: SMS RIS and OSD
    ... Installing RIS on Windows Server 2003 ... and path to where you want the RIS installation folder created in the Path ... Windows XP Service Pack 2 source files, ...
    (microsoft.public.sms.tools)
  • RE: Does RIS require a Microsoft DHCP server?
    ... Since I can't ever change that, I won't be able to use RIS since the DHCP ... server will point any PXE device, even a PC, at the phone server and the RIS ... What you do to authorize you RIS, if on another server, is open a DHCP MMC ...
    (microsoft.public.windows.server.general)
  • Re: RIS problem (or No RIS is the problem)
    ... I've not seen anything about the latest round of patches breaking RIS. ... As a test you may want to put down another image on the RIS server and see ... 317863 A RIS Client Installation May Hang at the "Setup Is Starting Windows ... the Remote Installation system service to install Windows 2000, Windows XP, ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Can you install RIS on a server running SMS, WSUS, and McAfee
    ... Why are you installing RIS if You have SMS ??? ... having to wait till i as able to buy a new server. ... version of the Windows Server 2003 family that you are installing. ... The volume on which you install RIS must be formatted with the NTFS ...
    (microsoft.public.sms.setup)