sysvol problem

A

ad

i manage (with MVP help) to run ad replication and everything was alright
until i found that sysvol dir isn't replicated.i cant acces it.
in event viewer i saw this log: Netlogon service could not create server
share G:\WINNT\SYSVOL\sysvol\xixixxum\SCRIPTS. The following error
occurred: The system cannot find the path specified.
i cant acces directory sysvol\sigillum
i checked \netlogon\parameters in registry - there was one missing
DynamicSiteName - i copy it from secondary dc but it change nothing.
Any ideas?

TIA
Ad
 
A

Ace Fekay [MVP]

In
ad said:
i manage (with MVP help) to run ad replication and everything was
alright until i found that sysvol dir isn't replicated.i cant acces
it.
in event viewer i saw this log: Netlogon service could not create
server share G:\WINNT\SYSVOL\sysvol\xixixxum\SCRIPTS. The following
error occurred: The system cannot find the path specified.
i cant acces directory sysvol\sigillum
i checked \netlogon\parameters in registry - there was one missing
DynamicSiteName - i copy it from secondary dc but it change nothing.
Any ideas?

TIA
Ad

Hi AD,

Can you post the Event ID # please?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
A

Ace Fekay [MVP]

In
ad said:
Hi Ace

event id : 5706

BTW thnx for help with replication

Regards
Ad

No problem AD. I was hoping it was all resolved after helping from the DNS
group.

See if this article helps out with this issue:
http://www.eventid.net/display.asp?eventid=5706&source=

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
A

ad

well i was really pissed off - i tried everything and nothing helps and i
.... delete mo domain folder under sysvol\sysvol dir
and recreate it - the error stop appearing but sysvol\mydomain is empty -
how to recreate it?


tia
ad
 
A

Ace Fekay [MVP]

In
ad said:
well i was really pissed off - i tried everything and nothing helps
and i ... delete mo domain folder under sysvol\sysvol dir
and recreate it - the error stop appearing but sysvol\mydomain is
empty - how to recreate it?


tia
ad

Haven't ran into this problem yet. I would suggest to copy if from your
other DC, but replication should have taken care of this anyway...

I guess you looked at those two MS tech articles mentioned in that link?
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q245086
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q258805

They deal with the reg entry. If you force replication in Sites and
Services, do any errors show up in the Event log?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
A

ad

I guess you looked at those two MS tech articles mentioned in that link?


well they didnt change anything
i try also ntfrs registry settings and nothing helps

my main problem is that the second dc server never replicate sysvol dir
cause since i started working on it it was broken on primary dc
well i try copy it and see what happens
sysvol on primary dc cant replicate with sysvol on secondary dc cause ther
are no dirs he is looking for

regards
ad
 
A

ad

ok i have copy sysvol from other dc

event manager - in replication i got event 13508 then after 2 minutes 13509
so i think it works
nothing else interesting except one event id 3019 - but i dont know if this
chanmge anything

now its time for silly question but i got lost : how to check if replication
works? i think it works but maybe its something i missed.

i saw some bad things in dcdiag but i am not sure what it means
heres report from replication monitor and dcdiag :

Active Directory Replication Monitor
Printed on 12/28/2003 2:14:34 AM
This report was generated on data from the server: RD21

***************************************************************************
RD21 Data
***************************************************************************

This server currently has writable copies of the following directory
partitions:
---------------------------------------------------------------------------
CN=Schema,CN=Configuration,DC=xixixxum
CN=Configuration,DC=xixixxum
DC=xixixxum

Because this server is a Global Catalog (GC) server, it also has copies
of the following directory partitions:
---------------------------------------------------------------------------

Current NTDS Connection Objects
-------------------------------
Default-First-Site-Name\domain2
Connection Name : 10a1e06c-41d0-4fd6-8a55-459cf6de50ad
Administrator Generated?: AUTO
Reasons for this connection:
Directory Partition (DC=xixixxum)
Replicated because the replication partner is a ring
neighbor.

Directory Partition (CN=Schema,CN=Configuration,DC=xixixxum)
Replicated because the replication partner is a ring
neighbor.

Directory Partition (CN=Configuration,DC=xixixxum)
Replicated because the replication partner is a ring
neighbor.


Current Direct Replication Partner Status
-----------------------------------------

Directory Partition: CN=Schema,CN=Configuration,DC=xixixxum

Partner Name: Default-First-Site-Name\domain2
Partner GUID: 7564DC39-0563-45A8-955C-7D7407709AB8
Last Attempted Replication: 12/28/2003 2:10:19 AM (local)
Last Successful Replication: 12/28/2003 2:10:19 AM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 6861
USN of Last Object Updated: 6861
Transport: Intra-Site RPC

Change Notifications for this Directory Partition
-------------------------------------------------
Server Name: Default-First-Site-Name\domain2
Object GUID: 28928B46-EA78-48E6-9DA9-1D430E27BDBD
Time Added: 6/22/2016 5:23:10 PM
Flags: DRS_WRIT_REP
Transport: RPC

Directory Partition: CN=Configuration,DC=xixixxum

Partner Name: Default-First-Site-Name\domain2
Partner GUID: 7564DC39-0563-45A8-955C-7D7407709AB8
Last Attempted Replication: 12/28/2003 2:12:56 AM (local)
Last Successful Replication: 12/28/2003 2:12:56 AM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 6938
USN of Last Object Updated: 6938
Transport: Intra-Site RPC

Change Notifications for this Directory Partition
-------------------------------------------------
Server Name: Default-First-Site-Name\domain2
Object GUID: 28928B46-EA78-48E6-9DA9-1D430E27BDBD
Time Added: 6/22/2016 5:23:10 PM
Flags: DRS_WRIT_REP
Transport: RPC

Directory Partition: DC=xixixxum

Partner Name: Default-First-Site-Name\domain2
Partner GUID: 7564DC39-0563-45A8-955C-7D7407709AB8
Last Attempted Replication: 12/28/2003 2:12:12 AM (local)
Last Successful Replication: 12/28/2003 2:12:12 AM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 6938
USN of Last Object Updated: 6938
Transport: Intra-Site RPC

Change Notifications for this Directory Partition
-------------------------------------------------
Server Name: Default-First-Site-Name\domain2
Object GUID: 28928B46-EA78-48E6-9DA9-1D430E27BDBD
Time Added: 6/22/2016 5:23:10 PM
Flags: DRS_WRIT_REP
Transport: RPC

Current Transitive Replication Partner Status
---------------------------------------------

Directory Partition: CN=Schema,CN=Configuration,DC=xixixxum

Partner Name: Default-First-Site-Name\domain2
Partner GUID: 7564DC39-0563-45A8-955C-7D7407709AB8
USN: 6938

Partner Name: **DELETED SERVER #2
Partner GUID: 841D6032-DDB5-4CF5-A685-B87F64D1C0E1
USN: 6709

Partner Name: Default-First-Site-Name\RD21
Partner GUID: C2BC830E-D90D-46D0-9D9B-7D2842CF1DA6
USN: 40492

Directory Partition: CN=Configuration,DC=xixixxum

Partner Name: Default-First-Site-Name\domain2
Partner GUID: 7564DC39-0563-45A8-955C-7D7407709AB8
USN: 6958

Partner Name: **DELETED SERVER #2
Partner GUID: 841D6032-DDB5-4CF5-A685-B87F64D1C0E1
USN: 6709

Partner Name: Default-First-Site-Name\RD21
Partner GUID: C2BC830E-D90D-46D0-9D9B-7D2842CF1DA6
USN: 40492

Directory Partition: DC=xixixxum

Partner Name: Default-First-Site-Name\domain2
Partner GUID: 7564DC39-0563-45A8-955C-7D7407709AB8
USN: 6953

Partner Name: **DELETED SERVER #2
Partner GUID: 841D6032-DDB5-4CF5-A685-B87F64D1C0E1
USN: 6709

Partner Name: Default-First-Site-Name\RD21
Partner GUID: C2BC830E-D90D-46D0-9D9B-7D2842CF1DA6
USN: 40492

Current Group Policy Object Status
----------------------------------
Default Domain Policy
Group Policy Object GUID: {31B2F340-016D-11D2-945F-00C04FB984F9}
Group Policy Object Version in the DS: 65539
Group Policy Object Version in SYSVOL: 65539

Default Domain Controllers Policy
Group Policy Object GUID: {6AC1786C-016F-11D2-945F-00C04fB984F9}
Group Policy Object Version in the DS: 3
Group Policy Object Version in SYSVOL: 3


The server RD21 knows about the following FSMO roles:
--------------------------------------------------------------------------
Schema FSMO: Default-First-Site-Name\RD21
Domain Naming FSMO: Default-First-Site-Name\RD21
Infrastructure FSMO: Default-First-Site-Name\RD21
Primary Domain Controller FSMO: Default-First-Site-Name\RD21
RID Pool FSMO: Default-First-Site-Name\RD21

Performance Statistics at Time of Report
----------------------------------------

Configuration (Registry)
NOTE: an empty value indicates that Windows 2000 will use the internal
default
NOTE: all empty values may indicate insufficient permission to retrieve this
information from the domain controller
------------------------

DSA
---

Days per Database Phantom Scan:
Initialize MAPI interface:
Enforce LIST_OBJECTS rights:
DSA Heuristics:
Max Threads (ExDS+NSP+DRA): 15
DSA Database file: G:\WINNT\NTDS\ntds.dit
DSA Working Directory: G:\WINNT\NTDS
Critical Object Installation:
DS Drive Mappings:
DSA Previous Restore Count: 1

REPLICATION
-----------

Replicator notify pause after modify (secs): 300
Replicator notify pause between DSAs (secs): 30
Replicator intra site packet size (objects):
Replicator intra site packet size (bytes):
Replicator inter site packet size (objects):
Replicator inter site packet size (bytes):
Replicator maximum concurrent read threads:
Replicator operation backlog limit:
Replicator thread op priority threshold:
Replicator intra site RPC handle lifetime (secs):
Replicator inter site RPC handle lifetime (secs):
Replicator RPC handle expiry check interval (secs):

LDAP
----

Max objects in LDAP Search (Admin Limit):
Max concurrent LDAP connections allowed:
Max time allowed for an LDAP Search:
Max concurrent LDAP searches allowed:
Max concurrent threads per LDAP connection allowed:
Minimum idle seconds before potential \ timeout of LDAP connection
(non-authenticated client):
Minimum idle seconds before potential \ timeout of LDAP connection
(authenticated client):

Database
--------

Database backup path: G:\WINNT\NTDS\dsadata.bak
Database backup interval (hours):
Database log files path: G:\WINNT\NTDS
Database logging/recovery: ON
Hierarchy Table Recalculation interval (minutes): 720
Database restored from backup:
Pending object ownership conversions:
EDB max buffers:
EDB max log buffers:
EDB log buffer flush threshold:
EDB buffer flush start:
EDB buffer flush stop:
EDB max ver pages (increment over the minimum:
Circular Logging:
Server Functionality:
TCP/IP Port:
Restore from disk backup:
Performance Counter Version: 10

KCC
---

Repl topology update delay (secs):
Repl topology update period (secs):
KCC site generator fail-over (minutes):
KCC site generator renewal interval (minutes):
KCC site generator renewal interval (minutes):
CriticalLinkFailuresAllowed:
MaxFailureTimeForCriticalLink (sec):
NonCriticalLinkFailuresAllowed:
MaxFailureTimeForNonCriticalLink (sec):
IntersiteFailuresAllowed:
MaxFailureTimeForIntersiteLink (sec):
KCC connection failures:
IntersiteFailuresAllowed:
IntersiteFailuresAllowed:

***************************************************************************
Enterprise Data
***************************************************************************

Globally Unique Identifiers (GUIDs) for each domain controller in the
enterprise
NOTE: the absence of a GUID means that the server has been demoted.
----------------------------------------------------------------------------
----

Site Name: Default-First-Site-Name
---------------------------------------
Site Options :
Site Topology Generator: CN=NTDS
Settings,CN=RD21,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CNConfigura
tion,DC=xixixxum
Site Topology Renewal :
Site Topology Failover :

RD21
Server GUID (used for DNS)
: 841D6032-DDB5-4CF5-A685-B87F64D1C0E1
Replication Database GUID (used to identify partner in
replication): C2BC830E-D90D-46D0-9D9B-7D2842CF1DA6
DSA Options : NTDSDSA_OPT_IS_GC
DSA Computer Path : CN=RD21,OU=Domain
Controllers,DC=xixixxum
DSA Schema Location :
CN=Schema,CN=Configuration,DC=xixixxum
DSA Mail Address :
_IsmService@841d6032-ddb5-4cf5-a685-b87f64d1c0e1._msdcs.xixixxum
DSA DNS Host Name : RD21.xixixxum
DSA BridgeHead Transports :

domain2
Server GUID (used for DNS)
: 28928B46-EA78-48E6-9DA9-1D430E27BDBD
Replication Database GUID (used to identify partner in
replication): 7564DC39-0563-45A8-955C-7D7407709AB8
DSA Options :
DSA Computer Path : CN=domain2,OU=Domain
Controllers,DC=xixixxum
DSA Schema Location :
CN=Schema,CN=Configuration,DC=xixixxum
DSA Mail Address :
_IsmService@28928b46-ea78-48e6-9da9-1d430e27bdbd._msdcs.xixixxum
DSA DNS Host Name : domain2.xixixxum
DSA BridgeHead Transports :



Site Links and Site Link Bridges
-----------------------------------------------------

Site Links
----------

Active Directory Replication Monitor determined that no Site Links
are present in the Directory.
Site Link Bridges
------------------

Active Directory Replication Monitor determined that no Site Link
Bridges are present in the Directory.
Inter-Site Transports
---------------------

IP
Options :
DLL Name : ismip.dll
Address Type: dNSHostName

SMTP
Options : NTDSTRANSPORT_OPT_IGNORE_SCHEDULES
DLL Name : ismsmtp.dll
Address Type: mailAddress

Subnets
-------
Active Directory Replication Monitor determined that no Subnets
are present in the Directory.
Active Directory Configuration Data
-----------------------------------
Stay of Execution for Servers: 0
SPN Mappings :
host=alerter,appmgmt,cisvc,clipsrv,browser,dhcp,dnscache,replicator,eventlog
,eventsystem,policyagent,oakley,dmserver,dns,mcsvc,
fax,msiserver,ias,messenger,netlogon,netman,netdde,netddedsm,nmagent,plugpla
y,protectedstorage,rasman,rpclocator,rpc,rpcss,remoteaccess,
rsvp,samss,scardsvr,scesrv,seclogon,scm,dcom,cifs,spooler,snmp,schedule,tapi
srv,trksvr,trkwks,ups,time,wins,www,http,w3svc,iisadmin











DC Diagnosis

Performing initial setup:
* Verifing that the local machine rd21, is a DC.
* Connecting to directory service on server rd21.
* Collecting site info.
* Identifying all servers.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\rd21
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... rd21 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\rd21
Starting test: Replications
* Replications Check
......................... rd21 passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=xixixxum
* Security Permissions Check for
CN=Configuration,DC=xixixxum
* Security Permissions Check for
DC=xixixxum
......................... rd21 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... rd21 passed test NetLogons
Starting test: Advertising
The DC rd21 is advertising itself as a DC and having a DS.
The DC rd21 is advertising as an LDAP server
The DC rd21 is advertising as having a writeable directory
The DC rd21 is advertising as a Key Distribution Center
The DC rd21 is advertising as a time server
The DS rd21 is advertising as a GC.
......................... rd21 passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=rd21,CN=Servers,CN=Default-Firs
t-Site-Name,CN=Sites,CN=Configuration,DC=xixixxum
Role Domain Owner = CN=NTDS
Settings,CN=rd21,CN=Servers,CN=Default-Firs
t-Site-Name,CN=Sites,CN=Configuration,DC=xixixxum
Role PDC Owner = CN=NTDS
Settings,CN=rd21,CN=Servers,CN=Default-First-S
ite-Name,CN=Sites,CN=Configuration,DC=xixixxum
Role Rid Owner = CN=NTDS
Settings,CN=rd21,CN=Servers,CN=Default-First-S
ite-Name,CN=Sites,CN=Configuration,DC=xixixxum
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=rd21,CN=Servers,
CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=xixixxum
......................... rd21 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2603 to 1073741823
* rd21.xixixxum is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1603 to 2102
* rIDNextRID: 1629
* rIDPreviousAllocationPool is 1603 to 2102
......................... rd21 passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/rd21.xixixxum/xixixxum
* SPN found :LDAP/rd21.xixixxum
* SPN found :LDAP/rd21
* SPN found :LDAP/rd21.xixixxum/xixixxum
* SPN found
:LDAP/841d6032-ddb5-4cf5-a685-b87f64d1c0e1._msdcs.xixixxum
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/841d6032-ddb5-4cf5-a6
85-b87f64d1c0e1/xixixxum
* SPN found :HOST/rd21.xixixxum/xixixxum
* SPN found :HOST/rd21.xixixxum
* SPN found :HOST/rd21
* SPN found :HOST/rd21.xixixxum/xixixxum
* SPN found :GC/rd21.xixixxum/xixixxum
......................... rd21 passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
* Checking Service: TrkSvr
* Checking Service: NETLOGON
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... rd21 passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
rd21 is in domain DC=xixixxum
Checking for CN=rd21,OU=Domain Controllers,DC=xixixxum in domain
DC=sig
illum on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=rd21,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=xixixxum in domain
CN=Configuration,DC=sigillu
m on 1 servers
Object is up-to-date on all servers.
......................... rd21 passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 12/28/2003 02:00:17
Event String: The File Replication Service is having trouble
enabling replication from domain2 to rd21 for
g:\winnt\sysvol\domain using the DNS name
domain2.xixixxum. FRS will keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
domain2.xixixxum from this computer.
[2] FRS is not running on domain2.xixixxum.
[3] The topology information in the Active
Directory for this replica has not yet replicated
to all the Domain Controllers.

This event log message will appear once per
connection, After the problem is fixed you will
see another event log message indicating that the
connection has been established.
An Warning Event occured. EventID: 0x800034C5
Time Generated: 12/28/2003 02:02:35
Event String: The File Replication Service has enabled
replication from domain2 to rd21 for
g:\winnt\sysvol\domain after repeated retries.
......................... rd21 passed test frssysvol
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15
minut
es.
......................... rd21 passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0xC0500006
Time Generated: 12/28/2003 01:57:19
Event String: vxboot: Failed to auto-import disk group
DynamicGroup. All volumes in the disk group are
not available.
An Error Event occured. EventID: 0x00000000
Time Generated: 12/28/2003 01:58:24
Event String: Server Administrator error: 126
An Error Event occured. EventID: 0xC0001B6F
Time Generated: 12/28/2003 01:58:24
Event String: The Secure Port Server service terminated with
the following error:
%%126
An Error Event occured. EventID: 0x00000000
Time Generated: 12/28/2003 01:58:24
Event String: Server Administrator error: 6
An Error Event occured. EventID: 0xC0001B58
Time Generated: 12/28/2003 01:58:24
Event String: The
Securom User Access for Windows 2000 and Windows XP a technology by Sony
DADC
service failed to start due to the following
error:
%%2
An Error Event occured. EventID: 0x0000002C
Time Generated: 12/28/2003 01:58:25
Event String: General database error occurred,
Can't initialize ESE instance - error -1811 JET_errFileNotFound, File not
found.

..

An Error Event occured. EventID: 0xC0001B70
Time Generated: 12/28/2003 01:58:25
Event String: The Terminal Services Licensing service
terminated with service-specific error 31.
......................... rd21 failed test systemlog

Running enterprise tests on : xixixxum
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the
scope
provided by the command line arguments provided.
......................... xixixxum passed test Intersite
Starting test: FsmoCheck
GC Name: \\rd21.xixixxum
Locator Flags: 0xe00001fd
PDC Name: \\rd21.xixixxum
Locator Flags: 0xe00001fd
Time Server Name: \\rd21.xixixxum
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\rd21.xixixxum
Locator Flags: 0xe00001fd
KDC Name: \\rd21.xixixxum
Locator Flags: 0xe00001fd
......................... xixixxum passed test FsmoCheck
 
A

ad

well dont read previous message - i think i was already sleeping

both dc seems to be working properly

thnx for help

Best Regards
Ad
 
A

Ace Fekay [MVP]

In
ad said:
well dont read previous message - i think i was already sleeping

both dc seems to be working properly

thnx for help

Best Regards
Ad

Well, then everything is ok now? Cool.... :)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top