In my case, deleting the existing computer account in AD and starting RIS again solved the problem.
Make sure the RIS server points to a valid OU (Organization Unit).
RIS had been working until I updated my server to Windows 2003 Service Pack 1. What I found was occurring is that after the login screen, the setup would take me straight to the image chooser menu. Previously, it had taken me to the computer name/OU customization screen. The error was being generated because SP1 changed RIS to automatically generate a computer name based upon the login credentials I had put in initially. My login had a special character, the ‘#’ symbol, which is invalid for a computer name, thus the error 1042.
To solve the problem, I had to edit the login.osc file in the \RemoteInstall\OSChooser\English directory and change the <FORM ACTION="CHOICE"> to <FORM ACTION="CUSTOM">. This restored my ability to manually input the computer name and OU location for the system.
I received this error infrequently after I renamed my RIS server. To fix the problem I followed the instructions in Microsoft’s ME260536
article, which included running “risetup –check”. Soon afterwards, I received EventID 1003 from source BINLSVC and everything returned to normal.
Launch AD, go to View -> Advanced Features, right click on the domain name, go to Security and give access to users or group on the AD domain for create object.
See the link below for troubleshooting change and configuration management.
From 2 newsgroups posts we found these:
Symptom: you cannot get past loon screen in RIS Client Installation Wizard. 1042/BINLSVC is recorded in the event log.
Cause: software error.
Workarround: type only the username and password at logon (do not type the domain name or
We expect that the information to be confirmed and the bug fixed by MS.