Re: AzMan & W2k3 SP1 problem...

From: Glenn LeCheminant (the.only(delete)_at_gmail)
Date: 07/04/05

  • Next message: Peter Rus: "Cannot set SE_DACL_AUTO_INHERITED flag"
    Date: Sun, 3 Jul 2005 15:07:26 -0700
    
    

    I doubt your issue has anything to do with azman.

    c:\windows\sysvol\sysvol>dir
    should report the domain folder as a junction folder.
    Verify that is still the case.

    Use linkd.exe to verify c:\windows\sysvol\sysvol\domainname is still linked
    to c:\windows\sysvol\domain

    Verify you can open the xml file in notepad from the junction directory.

    -- 
    Glenn LeCheminant
    CCNA, MCSE 2000/2003 + Security
    "UTT" <UTT@discussions.microsoft.com> wrote in message 
    news:666A6049-DEA7-45F6-BF7F-DB27846C8114@microsoft.com...
    > In W2k3 based domain-controller machine, I have a xml based Authorization
    > store (say abc.xml) under the <windir>\SysVol\domain directory. This file
    > also show up in the junction point <windir>\SysVol\SysVol\<domainname>
    > directory.
    >
    > Prior to installing SP1, I could able to run the azman.msc and open the
    > abc.xml store either by speciying the path
    > <windir>\SysVol\domain
    > -- or --
    > <windir>\SysVol\SysVol\<domainname>
    >
    > But, after installing SP1, the azman.msc behavior changes. Openning the
    > abc.xml store by specifying the path
    > <windir>\SysVol\domain is OK
    > -- but --
    > <winddir>\SysVol\SysVol\<domainname> throws the following ERROR.
    > "Cannot open the authorization store. The following problem occured. The
    > system cannot find the path specified"
    >
    > Does anyone out there know what is going on here? Is it something I have 
    > to
    > do to make it work or Is it a bug in the new version of azman libraries 
    > that
    > is shipped with the SP1?
    >
    > Any kind of advice is greatly appreciated. Thanks. 
    

  • Next message: Peter Rus: "Cannot set SE_DACL_AUTO_INHERITED flag"

    Relevant Pages

    • Re: AzMan & W2k3 SP1 problem...
      ... Reports correcly as a junction. ... > Verify that is still the case. ... >> abc.xml store either by speciying the path ...
      (microsoft.public.windows.server.security)
    • Re: Exchange 2003 Backup
      ... It is because you are backing up the store then the transaction logs. ... verify won't get to the transaction logs as they have been committed. ... Active backup destination: File ... Folder CHEESE\Microsoft Information Store\First Storage Group\Mailbox ...
      (microsoft.public.exchange2000.general)
    • Re: Uniqness of Hash Values
      ... If your software will be distributed to other people you cannot store the value as a constant in your code. ... You must use a second hash if you want to let someone else verify the integrity of one of your files. ... In order to verify the "salted" MD5 hash they would have to know the initial state, and that is supposed to be a secret. ...
      (borland.public.delphi.non-technical)
    • Re: Form that also updates the intermediary table?
      ... So I should get rid of the junction table tblsitelocation and store the site ... Should I just go back to 3 tables including the junction table? ... > EmployeeID foreign key to tblEmployee.EmployeeID ... rather than allenbrowne at mvps dot org. ...
      (microsoft.public.access.queries)
    • RE: FRSDiag v1.7 Tool, some error in AD 2003
      ... structure and junction points are correct. ... Verify that the following shared folders exist in the SYSVOL tree: ... There is a junction point must be linked to the \SYSVOL\domain folder. ... The LINKD command returns the following: ...
      (microsoft.public.windows.server.active_directory)