Recommendations on domain DR

I am in the process of documenting our WebLogic disaster recovery and have a couple of questions on best practice.
1) If my physical server crashes and I am attempting to get my WebLogic domain back up as soon as possible on another machine should I:
a) have the domain "unpacked" from the latest archive (that had a "pack" done on it)? (I assume WebLogic would have to be installed first on the new server and not be included in the domain unpack?)
b) have a full copy of the domain restored from a file copy of the domain? (This would no doubt have to have WebLogic installed first)
c) have the domain installed from a template that was built from template builder? ( I assume WebLogic would have to be installed as is not part of the template?)
('B' seems to be the fastest answer to me, but please confirm if there are caveats to this approach and if/why it would be better to use pack or template builder for this)
2) The assumption here would be that the IP addresses would be the same for the new machines, however, if they were not, would these just be a matter of updating the config.xml to the new IP address? Or would there be more to consider?
3) If the environment is clustered do you make templates (or pack jar) on both servers? ( These 2nd clustered servers ARE enrolled in the domain and therefore have a domain, config.xml.etc...as well).
Thanks in advance for any experience or knowledge on the preferred way to handle this....

Hi
1. I would not recommend unpack approach. First thing is, YES, you do need to install Weblogic Sever exactly same version. Then run unpack command. But the main issue is packing and unpacking may not copy all the resources of the domain configuration like any JDBC data sources, AD settings/configurations, JMS stuff etc. If I am not wrong generally we use pack/unpack to create the Managed Servers on the remote machines in a clustered env.
2. Yes, copying full domain folder completely is a quick and kind of reliable way to get back into business. Ofcourse, you need to have Weblogic Server same version installed in the exact same folder structure. Also if you have any external JDKs, you have to install them also. Now if IP address is different, just modify config.xml file to update the new IP Address. That is the only location.
3. Template approach is mostly during the Development phase. We create a domain, configure all the stuff. Then export it as a Template. On remote other machine, first install weblogic server. Run config wizard and create new domain based on that template. Now, some of the things are configurable again like password etc for domain. But point is, you had to do some extra work like creating domain etc.
4. If Env is Clustered, still you make Template or Pack only from the main master machine that has AdminServer and all other configurations. Because all the remote or other machines having managed servers, just get a copy of master admin machine everytime. So managed servers is just a copy but not the original.
So ideally, having a regular backup of domain folder and using that is a quick solution. If this fails, use Template approach. If this fails, last option is pack/unpack.
Thanks
Ravi Jegga

Similar Messages

Need recommendation regarding domain admin permission

Hi,
Recently we got the request from IT security team to remove domain admin privileges for any IT user account even Sr. System Administrator. As per them it is not recommended to login with domain admin account on workstation so they asked me to create
standalone account for workstation and use domain admin account only for login to servers.
I need someone recommendation regarding this and if yes then please mention some points why it not recommended to have domain admin privileges for System Administrator for daily usable account.
Appreciate your quick response regarding them.
Regards,
Hakim. B
Hakim.B Sr.System Administrator

1. Do not provide the domain admin permission more that 3/4 persons. No matter however big is the env.
2. ADDS Audit should be enabled.
ADDS 2008 Audit
3. Restricted group is ok but that is overwritten the existing admins.
Regards,
Biswajit
MCTS, MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, Enterprise Admin, ITIL F 2011
Blog:
Script Gallary:
LinkedIn:
Note: Disclaimer: This posting is provided & with no warranties or guarantees and confers no rights..

Domain alias in iMS 5.2

Hi,
Objective: The Users of Domain abc.com want that mails can be sent to them at xyz.com domain too.
Methods: flat alias file (not recommended)
vanity Domains ( fit for small no of users only)
Domain Alias ( recommended)
Discussion:
I created a Domain alias for abc.com to be xyz.com
ldif used
=======
dn: dc=xyz,dc=com,o=internet
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=abc,dc=com,o=internet
dc: xyz.com
ldapmodify -a -D "cn=Directory manager" -w mypassword -f aboveldiffile
My option.dat has entries for aliasurl and alias magic
Now I try to login using user@xyz : success
I try to send mail to user@xyz instead of [email protected]: failure
What happens ..in directpry access logs:
dc root is checked for xyz domain ...on finding ...the search base is adjusted to abc.com....
But now the e-mail address searched for is [email protected]..in domain abc ...which is not set ...
SO I DEFINE ALTERNATEMAILADDRESS ATTRIBUTE FOR DOMAIN USERS ABC.COM
so that search matches...
Now things work fine ....
I also check some postings here on the sunbject ....
where JAY suggests to use DOMAIL_LEVEL = 2 in option.dat file..
I delete mailalternateaddresses ...for users add DOMAIN_UPLEVEL=2...
now sendinf mail addressed at [email protected] suceeds....
Looing at ldap access logs I find ...that the search is directly started at abc.com ???
and the mails searched for are [email protected] aswell as [email protected] ...
So my concern is WHAT DOES DOMAIN_LEVEL actually DO????
Thanks

For a very good description of how direct ldap works, please see here:
http://docs.sun.com/source/816-6009-10/dirldap.htm#27650

Samba problems between two linux computers

I have a laptop with arch with this smb.conf
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = Samba Server
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
wins support = no
[homes]
comment = Home Directories
browseable = yes
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[Themes]
path = /home/du/Themes
available = yes
browsable = yes
public = yes
writable = yes
and another pc with ubuntu with this smb.conf
# Sample configuration file for the Samba suite for Debian GNU/Linux.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
; domain logons = yes
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home director as \\server\username
[homes]
comment = Home Directories
browseable = yes
writable = yes
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
read only = no
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# The following parameter makes sure that only "username" can connect
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = yes
; create mask = 0600
; directory mask = 0700
[printers]
comment = All Printers
browseable = yes
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
# The CD-ROM gets unmounted automatically after the connection to the
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
[Downloads]
path = /home/Duccio/Downloads
available = yes
browseable = yes
guest ok = yes
public = yes
writable = yes
Both have static ip
The problem are 2:
1- the pc cant see eachothers with nautilus under "network" but..
2- if i type in nautilus in the address bar from the arch pc "smb://ubuntu_ip" i can see shared folders the shared folder in ubuntu pc /home/Duccio/Downloads is browseable but i cant mount folders, the message is "unable to mount location"
Another pc with ubuntu wich have dhcp is visible under nautilus network
Last edited by jacopastorius82 (2010-11-02 21:14:51)

in laptop pc with arch i have installed somewhat in gnome under System-->administration called "shared folder". Maybe this sort of software override manual configuration in /etc/samba/smb.conf?
Something like that is probably standing in ubuntu as well i suppose..
Last edited by jacopastorius82 (2010-11-03 22:13:53)

Mounting shares with nautilus

When I was using Ubuntu a few months ago Nautilus automatically mounted shared folders. That was really convenient and I'm trying to figure out how to do this on Arch. My shared folder icon comes up but when I try to open it I get the error, Unable to Mount Location: Failed to mount windows share.
I browsed the forum and the wiki looking for answers. I've messed with the samba.conf file and can't seem to get this to work. I even copied my roommates smb.conf from his computer running Ubuntu. Here's the smb.conf:
# Sample configuration file for the Samba suite for Debian GNU/Linux.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentary and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
; wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = true
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
; syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
; security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
; guest account = nobody
invalid users = root
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how nsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
; domain logons = yes
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
; logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
; logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
; load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
; domain master = auto
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
usershare owner only = False
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
#[printers]
# comment = All Printers
# browseable = no
# path = /var/spool/samba
# printable = yes
# guest ok = no
# read only = yes
# create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
#[print$]
# comment = Printer Drivers
# path = /var/lib/samba/printers
# browseable = yes
# read only = yes
# guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
; write list = root, @ntadmin
# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
# The CD-ROM gets unmounted automatically after the connection to the
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
[usershares]
comment = Video Folder
path = /home/cd/video
read only = no
browseable = yes
writable = yes
public = yes
guest ok = yes
available = yes
usershares max shares = 100
usershares owner only = False

I'm having the same issue here, though not just in Nautilus.
Samba is working to some extent because I can access the directories I'm sharing on both of my Linux computer from a Windows laptop with no trouble. Come to think of it the Windows laptop (running XP) and my VirtualBox, also running XP, both access the samba shares fine.
However, I can not access them from the Linux computers. I have two Linux machines actually, Avalon and Atlantis. The one, Avalon, I can't access anything from/on (though Windows can access it just fine). The other one, Atlantis, I am sharing /homes and /srv, /srv mounts fine, but /homes will not. I'm sharing /srv on Avalon as well, but it won't mount.
To simplify, /srv on Atlantis is the only share I can access from either Linux machine. But only the /srv on Atlantis, not the /srv on Avalon.
I have smbnetfs installed. Here are my daemons from rc.conf:
DAEMONS=(syslog-ng network netfs smbnetfs crond dbus hal fam alsa mysqld mythbackend mpd openntpd lircd cups httpd sshd privoxy tor samba gdm)
I am curious though: does netfs and smbnetfs need to be running?
Any help would be appreciated. Thanks.
Frantic wrote:You should check your logs and see why the mount is failing, it's probably a small tweak (maybe fuse not loaded)
Probably something I should know already, but what logs should I check? Thanks.
Last edited by The Avatar of Time (2009-03-06 10:16:03)

Screen Sharing to Device with iCloud

Prior to Yosemite, every machine associated with my iCloud ID would show up in the Finder under "Sharing". If I selected that machine's name, I'd see the shared folders, and be able to activate Screen Sharing directly to that machine with a button click.
Since upgrading to Yosemite, I no longer see these machines available to connect-to. I've tried disabling and re-enabling "Back to my Mac". I've also upgraded the Server service running on the host machine I'd planned to connect-to in case that was a factor, but it hasn't resolved the problem.
Anybody know how to get iCloud-linked machines to show up under Sharing in the Finder so I can easily establish Screen Sharing connections?
Thanks

If you changed nothing other than to update your client Mac to Yosemite, what you describe strongly resembles an earlier bug making an encore appearance.
What follows is what I had to say about it roughly a year ago, updated for today. Some of it will be obvious to experienced Mac users so overlook that.
This can be a challenging problem to diagnose. It appears that Mavericks Yosemite has changed something about BTMM resulting in it being less reliable than it was with Mountain Lion Mavericks. It works, but not always, and I have yet to correlate its cause to anything specific.
Here are some possible hints.
Make sure you are using a compatible router. BTMM requires a router that supports NAT Port Mapping Protocol (NAT-PMP) or Universal Plug and Play (UPnP). Most routers will work without any trouble at all, but an Apple AirPort will eliminate any uncertainty.
Review all the steps in OS X: Using and troubleshooting Back to My Mac with your iCloud account
The most useful suggestion may be the simplest:
Toggle Back To My Mac off and back on by deselecting and then reselecting Back To My Mac in iCloud System Preferences.
Sometimes that's all it takes.
You can also try some simple steps with Terminal to verify that your BTMM settings are correct:
dns-sd -B _rfb | grep icloud
That will show the Macs using your iCloud ID advertising screen sharing services. If you get no response, ensure the Sharing services on the Macs you wish to use remotely are configured correctly. Perhaps Mavericks simply reverted their settings during installation, as a "security" measure.
dns-sd -B _afpovertcp will show Macs advertising file sharing services.
To ping your Mac use:
ping6 <macname>.<nnnnnnn>.members.btmm.icloud.com
where <macname> is the name of your Mac and <nnnnnnn> is your Back to My Mac account number. See below. You should get a response from ping6; if there is none then screen or file sharing will not work. If the response times are excessively long then the connection may time out and fail.
The name of your Mac is in System Preferences > Sharing > Computer Name:
Your Back to My Mac account number can be determined with the following
dns-sd -E
It will respond with something like this
Timestamp    Recommended Registration domain
0:43:20.322 Added    (More)              local
0:43:20.322 Added    (More)              icloud.com
                                            - > btmm
                                            - - > members
                                            - - - > 0123123
0:43:20.322 Added                          icloud.com
                                            - > btmm
                                            - - > members
                                            - - - > 987654321
The numbers at the end (0123123 etc) are your BTMM account numbers. Most users will have only one.
^C to terminate each of the above.
Good luck.
An example of the above is as follows. Assuming your iCloud ID is 123456 and the Mac you're trying to connect to is named MyMac the above ping6 command is
ping6 MyMac.123456.members.btmm.icloud.com
You should get a response.
You can also try to login to the remote Mac using ssh. Assuming your login name is telstar that would be
ssh -l telstar MyMac.123456.members.btmm.icloud.com
Both should work regardless of your location, whether both Macs are on the same LAN or separated by thousands of miles makes no difference because they are using iCloud services and not local Bonjour to access the remote machine.
Given that your Mac is not appearing in a Finder Sidebar under "shared" I doubt either of the above will work for you.
Report it to Apple. The problem may be related to the particular model Mac you are using, or not.
That's all I have to offer.

RE: iWeb with private host or .mac

can any one give me advice I am on a trial.mac account which I have not even had time to look at what it offers but my account runs out in 26 days and I just finished my web site I made with Iweb I want to buy a domain for my site now
and not sure if I should just stay with .mac or get another host?
Also if I don't stay with .mac who do recommend for hosting?
Or who do you recommend for domain purchases?
Imac 5 Mac OS X (10.4.3)

I use Media Temple, they're great: http://www.mediatemple.net/services/webhosting/ss/linux-standard/
15% hosting discount here: http://www.kirupa.com/mt.html
FYI: If you allow your .Mac trial account to expire, you can still use the username in iChat.

What is the best practice and Microsoft best recommended procedure of placing "FSMO Roles on Primary Domain Controller (PDC) and Additional Domain Controller (ADC)"??

Hi,
I have Windows Server 2008 Enterprise and have
2 Domain Controllers in my Company:
Primary Domain Controller (PDC)
Additional Domain Controller (ADC)
My (PDC) was down due to Hardware failure, but somehow I got a chance to get it up and transferred
(5) FSMO Roles from (PDC) to (ADC).
Now my (PDC) is rectified and UP with same configurations and settings. (I did not install new OS or Domain Controller in existing PDC Server).
Finally I want it to move back the (FSMO Roles) from
(ADC) to (PDC) to get UP and operational my (PDC) as Primary.
(Before Disaster my PDC had 5 FSMO Roles).
Here I want to know the best practice and Microsoft best recommended procedure for the placement of “FSMO Roles both on (PDC) and (ADC)” ?
In case if Primary (DC) fails then automatically other Additional (DC) should take care without any problem in live environment.
Example like (FSMO Roles Distribution between both Servers) should be……. ???
Primary Domain Controller (PDC) Should contains:????
Schema Master
Domain Naming Master
Additional Domain Controller (ADC) Should contains:????
RID
PDC Emulator
Infrastructure Master
Please let me know the best practice and Microsoft best recommended procedure for the placement of “FSMO Roles.
I will be waiting for your valuable comments.
Regards,
Muhammad Daud

Here I want to know the best practice
and Microsoft best recommended procedure for the placement of “FSMO Roles both on (PDC) and (ADC)” ?
There is a good article I would like to share with you:http://oreilly.com/pub/a/windows/2004/06/15/fsmo.html
For me, I do not really see a need to have FSMO roles on multiple servers in your case. I would recommend making it simple and have a single DC holding all the FSMO roles.
In case if
Primary (DC) fails then automatically other Additional (DC) should take care without any problem in live environment.
No. This is not true. Each FSMO role is unique and if a DC fails, FSMO roles will not be automatically transferred.
There is two approaches that can be followed when an FSMO roles holder is down:
If the DC can be recovered quickly then I would recommend taking no action
If the DC will be down for a long time or cannot be recovered then I would recommend that you size FSMO roles and do a metadata cleanup
Attention! For (2) the old FSMO holder should never be up and online again if the FSMO roles were sized. Otherwise, your AD may be facing huge impacts and side effects.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password

Please recommend the best free domain compatible with iweb

can someone recommend a free domain where i can host my site? i would like to make the website with iweb. please also tell me how to upload it to that domain. just a general idea would be enough.
thanks for your time.
Neerav

To upload to such server you need a ftp application.
[Cyberduck|http://cyberduck.ch] is the recommended one.

Is it recommended practice to add SCCM service accounts to the Domain Admins group?

I am working with an external consultant that is recommending that all of the SCCM service accounts be added to the Domain Admins group. I am not the SCCM engineer, I am the AD guy, this is the reason I am questioning this methodology. I have
read several articles that seem to provide the appropriate configuration options for all of the SCCM accounts so I see no need to allow these accounts to have Domain Admin level access to the environment. I don't see a reason for ANY of the service accounts
to have Domain Admin, let alone all of them. I have referenced several TechNet articles but there does not seem to be definitive guidance around this. Could anyone assist with settling this? Thanks in advance.

No, there's absolutely no reason for the service accounts to be domain admins.
All of the required service accounts used in a SCCM environment can be given the proper permissions given their purpose.
Example: Join Domain Account can be given the permissions to join computer objects in the very specific OU in AD, and nothing else.
Network Access Account only need read access to your distribution points.
Client Push Account needs local administrative permissions on your clients.
What i'm trying to say is. None of any of the service accounts needs to be domain admin. Hope that helps.
Martin Bengtsson | www.imab.dk

Recommended DNS zone replication scope for single domain environment

Hi, in my company we have domain/forest functional level Windows Server 2008 R2 - there is only one domain. AD DS is installed on 5 servers -
AD integrated DNS zone is used.
I noticed today that on both forward lookup DNS zones, _msdcs.internaldomain.com
& internaldomain.com, zone replication scope was set to
All DNS servers in this domain and also for one reverse lookup zone. I changed this setting for all these zones to
All domain controllers in this domain but later (10-15 mins at most) I reverted these settings back to
All DNS servers in this domain.
Which zone replication scope for mentioned zones is recommended keeping in mind this is single domain environment? Also could I do any harm to DNS and AD in all when I changed zone replication scope and later reverting it back for these zones? How to check
that dns related informations (zones) are located where they should be in Active Directory and that there is no any garbage in other locations (partitions) in AD database.

Hi,
All DNS servers in this domain : Replicates zone data to all Windows Server 2003 and Windows Server 2008 domain controllers running the DNS Server service in the Active Directory domain. This option replicates zone data
to the DomainDNSZone partition. It is the default setting for DNS zone replication in Windows Server 2003 and Windows Server 2008.
http://technet.microsoft.com/en-us/library/cc772101.aspx
Hope this helps.
Regards.
If you have any feedback on our support, please click
here
Vivian Wang

Domain & Web Host Questions? Recommendations

Hi, I've been looking to purchase a domain name for my
portfolio site and have it hosted seperately. I've had plenty of
luck finding good review sites for hosting companies but none
concerning registrars. What domain registrars would you suggest
(excluding GoDaddy)? Also, when looking for a hosting company how
do I find out if dreamweaver sites are compatible? Any feedback
would be much appreciated!

That's who I use....
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Mad Dog" <[email protected]> wrote in
message
news:f6mm4b$srv$[email protected]..
> BTW, that's Dotster for domain registration only.
>
> Mad Dog wrote:
>> I highly recommend www.dotster.com. Anyone second
that?
>>
>> MD
>>
>>
>> medeine wrote:
>>> Hi, I've been looking to purchase a domain name
for my portfolio site
>>> and have it hosted seperately. I've had plenty
of luck finding good
>>> review sites for hosting companies but none
concerning registrars.
>>> What domain registrars would you suggest
(excluding GoDaddy)? Also,
>>> when looking for a hosting company how do I find
out if dreamweaver
>>> sites are compatible? Any feedback would be much
appreciated!
>
>

Intermittent connection to domain from remote site.. What is the recommended solution?

Hello,
I used to have a separated branch office with its own application/db standalone server, and about 15 users locally configured on that server...
Recently we implemented a Microwave connection (25 Mbps) between the main and branch office, joined the server of the branch office as a member server of the main office domain and add users' accounts to the domain. So now remote users have there logon
and credentials from the DC in the main office but still work on there application/db member server located on the branch office.
The problem in this design is that when the connection occasionally goes down, users can't work on their application although there server is located on their same LAN, because they can't gain the necessary credentials from the DC/GC on the main site!!!
Would you please suggest any solution for this problem... do I have to make a local DC in the branch office, or create Child domain, or what?
PS.. I'm working on Windows 2003 domain
Thank you all

Greetings!
If you are not running low on budget and bandwidth is not a concern, consider implementing an additional domain controller in your branch office and make it as global catalog.
Regards.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Any applicable\recommended Group Policy settings (Local & Domain) for configuring windows 8.1 "gold master image" for collection

Happy Friday everybody -
I'm working on implementing Microsoft RDS 2012\VDI for the folks here at work. I've read - online - a lot of articles on VDI and RDS 2012 - and have a working model that is working somewhat satisfactorily. I haven't seen much online about steps
I could take in Local Group Policy on my Windows 8.1 'gold image' - or for that matter Domain level group policy - that can assist in creating a better, more reliable/robust Windows 2012 VDI environment.
Anybody out there got any information or opinions or advice on Group Policy settings for VDI environments?
Thanks again, everyone!
Adrian
anr

Hi Adrian,
Thank you for posting in Windows Server Forum.
In regards to your issue you can refer beneath article for detail information.
1. Group Policy Best Practices for VDI Environments
2.Some Basic Group Policy Settings for VDI
Hope it helps!
Thanks.
Dharmesh Solanki

Recommended Specs for Active Directory Domain Controllers?

Duffney wrote:Sosipater wrote:Duffney wrote:
Good to know, most have around the specs you're all recommending. Most have extremely high CPU reading, however I've found out that it's a security software causing this.Best practices would be that a DC run no more than AD DS, DNS, and DHCP.
Good point, I should also write a script to query the roles of each DC and work to migrate extra roles off it.Unless you're bouncing off of licensing limits, there isn't a good reason any more to run anything extra on your DC if you're virtualized.

Sosipater wrote:Duffney wrote:
Good to know, most have around the specs you're all recommending. Most have extremely high CPU reading, however I've found out that it's a security software causing this.Best practices would be that a DC run no more than AD DS, DNS, and DHCP.
Good point, I should also write a script to query the roles of each DC and work to migrate extra roles off it.

Recommendations on domain DR

Similar Messages

Maybe you are looking for