oidgen.exe - available for public download?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have been searching for the oidgen.exe (OID Generator) utility, which
reportedly ships with the Windows Server 2000 resource kit, without much
success. I am aware that the Microsoft web site only makes certain tools
available for download; however I have been able to only find one
(irrelevant) reference to this utility in the online support site.

If anyone has more information about this utility, including where I may
find it without buying the entire Resource Kit, please let me know!

Thanks,
~Mark
 
Jorge -

I appreciate your response, but it does not address my question. I am fully
aware of the process of registering an OID branch with Microsoft, and of the
implications of generating your own OID (collision, etc.) However, my
project is of a classified nature and as such, we feel that using an
anonymous OID is the best solution. We do not intend to deploy this
solution, so there will be no OID conflict issues when using this utility.

Please let me know if there's anything else you need!
~ Mark
 
Mark said:
Jorge -

I appreciate your response, but it does not address my question. I am fully
aware of the process of registering an OID branch with Microsoft, and of the
implications of generating your own OID (collision, etc.) However, my
project is of a classified nature and as such, we feel that using an
anonymous OID is the best solution. We do not intend to deploy this
solution, so there will be no OID conflict issues when using this utility.
Click to expand...

I don't know what the full implications are of using oidgen.exe because
I'm not familiar with the program, however, if you really intend for
your project to never (can you guarantee that? what happens if you add
in a product that modifies your schema to use the same OID branch you
end up choosing?) go outside of a classified nature then why not just
pick a currently unused OID branch and start using it?

I'd still suggest registering a branch because your project may never go
classified but if you ever bring in a COTS product that uses the same
OID branch you hijacked then you may run into a problem.
 
Back
Top