NEWBIE How to apply settings using secedit

From: Paul (plangton@start.com.au)
Date: 01/02/03


From: plangton@start.com.au (Paul)
Date: 1 Jan 2003 21:14:01 -0800


Hi All,

I've been given two .inf and one .db file and asked to apply to non
network connected workstations. One the the standard hi security
workstation stuff,m and the other set builds on that apparently. I
don't relaly have any idea how to apply these, but having read lots of
confusing documentation I've seen that the secedit command should do
this. So I've set it up to run the following commands:

secedit /configure /cfg securews.inf /db sec1.sdb /verbose
secedit /configure /cfg LMS_kiosk_hisecws.inf /db sec1.sdb /verbose

However nothing at all seems to happen. How would I apply just the hi
security workstation settings??

Rgds

Paul



Relevant Pages

  • Paradigms II
    ... Secure Systems Revisited ... Performing the following very basic security evaluation on your system ... (server or workstation); however, they can be easily adapted to any other ... control over that information. ...
    (comp.security.misc)
  • Re: Paradigms II
    ... > are not about trying to circumvent security. ... > (server or workstation); however, they can be easily adapted to any other ... > to have at least a vague idea what security, and a secure environment, ...
    (comp.security.misc)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... In my experience what you have done with security policy should ... The workstation gets its networking information from DHCP that, ... updates DNS. ... I don't believe the problem to be at the server end though. ...
    (microsoft.public.win2000.security)
  • Re: Upgraded from SBS2K to 2K3: Connectcomputer Wont on XP client
    ... Could it be security issue? ... > Decided to upgrade the office network for practice. ... > workstation, a fully patched XP pro which had been working flawlessly on ... the server shows them (but ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... manual inspection of the DNS _srv records plus NSLOOKUP from the workstation ... In my experience what you have done with security policy should ... not interfere with that computer being able to find a domain controller. ... updates DNS. ...
    (microsoft.public.win2000.security)