Lion server migration from 10.6 wiki dead, mail dead, ical dead

i have a mac mini w leopard server- everything worked perfect
i upgrade and migrated to lion server
nothing working, wiki, mail, or icalendar
any ideas-
other than going back to restore of timemachine of leopard server
thanx
CT

One thing that jumps out from your brief description of the problem is a bug in the persent iteration of Lion Server that occurs when the "Dedicate system resources to server services" box is checked (or, honestly, when it's unchecked too -- read on). This is located within Server.app. in the left pane, select your machine under the hardware section. The second tab, settings, contains this option. I'd try either ticking or unticking the box and then restarting and then trying to start those services again. Though the bug was initially reported as related to this similar problem (the one you describe) occurring when this box is checked, I've found that toggling between on to off, or off to on (depending on the current state) and then restarting, seems to help get things going again. Sometimes this has to be done twice. As well, until Apple issues a fix for these Server.app related problems, it's best, once you get your server configured, to keep from opening Server.app when possible. Just opening it seems to cause problems. One example of this is checking the mail quota box and entering a value. It seems to stick fine, but when Server.app is opened again, the box is unchecked once again. This one happens every time.

Similar Messages

Wiki server migration from 10.5 to 10.6.2

I have upgraded our xServe server from 10.5.x to 10.6.2. I was also able to migrate our wiki pages. When I tried to "comment" on a wiki page, I am getting the following message.
Error from server: table discussions has no column named unauthenticated (8002)
Looking at the wiki log, this is the error message that is being displayed.
http://HTTPChannel,4,127.0.0.1 Unhandled Error
Traceback (most recent call last):
File "/usr/share/caldavd/lib/python/twisted/web/http.py", line 720, in requestReceived
self.process()
File "/usr/share/caldavd/lib/python/twisted/web/server.py", line 126, in process
self.render(resrc)
File "/usr/share/caldavd/lib/python/twisted/web/server.py", line 133, in render
body = resrc.render(self)
File "/usr/share/wikid/lib/python/applexmlrpcserver/WebAppServer.py", line 87, in render
d = defer.maybeDeferred(function, request, *args)
▪ <exception caught here> ---
File "/usr/share/caldavd/lib/python/twisted/internet/defer.py", line 104, in maybeDeferred
result = f(*args, **kw)
File "/usr/share/wikid/lib/python/applexmlrpcserver/DiscussionService.py", line 117, in xmlrpc_addDiscussionEntry
aUID = aDiscussion.addEntry(entryDictionary'subject', entryDictionary'content', author = author, unauthenticated = unauthenticated, moderated = moderated, parent = parent)
File "/usr/share/wikid/lib/python/applexmlrpcserver/Discussion.py", line 153, in addEntry
anIndex.addDiscussionEntry(self.data'entries'entryID)
File "/usr/share/wikid/lib/python/apple_utilities/DiscussionIndex.py", line 62, in addDiscussionEntry
con.cursor().execute('INSERT INTO discussions(parent, moderated, content, author, uid, unauthenticated, time) VALUES (?, ?, ?, ?, ?, ?, ?)', values)
sqlite3.OperationalError: table discussions has no column named unauthenticated
Has anyone migrated their wiki pages w/o any issues? Could one migrate their wiki server pages from 10.5.x to 10.6?
Thanks,
Thomas

When I upgraded our server (which was solely a Wiki server), I simply grabbed the Collaboration directory on the old server, wiped it, set up a new server with the same group and wiki name, examined the permissions on the empty Wiki it created, pasted in the old Collaboration folder, tweaked the permissions, and it worked fine.

Will Lion server update from SL server maintain wiki contents?

I would like to know if the upgrade to lion server from SL server will erase or make unusable the contents of my Wikis, blogs and websites. What would I have to do to preserve them as functioning services if I upgrade to Lion Server?

Thanks, I don't have a good handle on this. Here is the tail of named.log while problem was happening and even during the start. Perhaps, it is running, but server admin doesn't think so and lots of other services are hung or turn themselves off (web, wiki, profile manager ...)
03-Aug-2011 21:54:43.991 createfetch: local SOA
03-Aug-2011 21:56:36.762 createfetch: local SOA
03-Aug-2011 21:56:36.794 decrement_reference: delete from rbt: 0x10d8727e0 clients.l.google.com
03-Aug-2011 21:57:09.537 createfetch: safebrowsing.clients.google.com A
03-Aug-2011 21:57:09.574 createfetch: clients.l.google.com A
03-Aug-2011 21:57:09.601 decrement_reference: delete from rbt: 0x10d872780 clients1.google.com
03-Aug-2011 21:57:11.769 createfetch: safebrowsing.cache.l.google.com A
03-Aug-2011 21:57:55.591 createfetch: ytstatic.l.google.com A
03-Aug-2011 21:57:55.631 decrement_reference: delete from rbt: 0x10d639738 ssl.gstatic.com
There isn't much here to look at.
changeip -checkhostname does work when this occurs.
Also, open directory stays running.
Thanks again!

Upgrade from Lion Server to ML 10.8.1 Broke Mail server!

....10.8.1 OD seems to work, files and AFP available, but Mail server not working correctly. Now users don't see mail, postfix issues numerous errors about missing system_user_maps and delivers no mail? Must recover mails! Help! Where should I look, and what to read for Diagnosis ?
After upgrade in place from SL to Lion to ML. most services did not work correctly; except for Mail and DNS and OD.   Reinstalled.   Now most everything seems to work including Card Services, Calendars, Wiki, Web, DNS, OD. But Mail is off and missing??? No delivery of INcoming mail, No Sending Mail, no IMAP Mail login for users.
On Mail configuration in Server.App: Turned off All Filtering. Have rebooted Server several times, Restarted Mailserver from Server,app and Terninal.   Same Results. Somewhere along the line from Server 10.5 to SL to Lion to 10.8 incoming Maill started going to [email protected] rather than simply [email protected].
    Is it possible that virtual domains are fuzzing up the works? The error logs use the longer virtual domain (with the sevrer name prefix) rather than the domain name?
Here are some sample Log messages:
From SYStem Log:
Sep 7 19:33:56 plg1.plg-law.com postfix/cleanup[1998]: warning: 8273B199E3F8: recipient_canonical_maps map lookup problem for [email protected]
Sep 7 19:33:56 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/ECF3A196A4FE: error writing 8273B199E3F8: queue file write error
Sep 7 19:33:58 plg1.plg-law.com postfix/pickup[1324]: warning: E5AC9199E3F9: message has been queued for 1 days
Sep 7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep 7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep 7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: E5AC9199E3F9: recipient_canonical_maps map lookup problem for [email protected]
Sep 7 19:33:58 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/ED4AB196A4FF: error writing E5AC9199E3F9: queue file write error
Sep 7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep 7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep 7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: 385DD199E3FB: recipient_canonical_maps map lookup problem for [email protected]
Sep 7 19:33:59 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/EE2A9199B211: error writing 385DD199E3FB: queue file write error
From SMTP Log:
Sep 7 19:35:24 plg1.plg-law.com postfix/pickup[1324]: 3652E199E487: uid=78 from=<_mailman>
Sep 7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep 7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep 7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: 3652E199E487: recipient_canonical_maps map lookup problem for [email protected]
Sep 7 19:35:24 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/8E82B199AD06: error writing 3652E199E487: queue file write error

here's my configured postfix main.cf file from /etc/postfix/main.cf   (mountain lion server 10.8.1)
Server.app should have somewhat configured it correctly for you in someways, but something got messed up in the import script I guess.
Hope this helps...
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /Library/Server/Mail/Data/spool
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /Library/Server/Mail/Data/mta
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
#          mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in
#   the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
           PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
           xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
#          PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
#          echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
#          >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
#          PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
#          -dmS $process_name gdb $daemon_directory/$process_name
#          $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = _postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = /usr/share/doc/postfix/html
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
#======================================================================
# dovecot
dovecot_destination_recipient_limit = 1
# default mailbox size limit set to no limit
mailbox_size_limit = 0
# List of ciphers or cipher types to exclude from the SMTP server cipher
# list at all TLS security levels.
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
# Protect SSL/TLS encryption keys
tls_random_source = dev:/dev/urandom
# (APPLE) Credentials for using URLAUTH with IMAP servers.
imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
# (APPLE) The SACL cache caches the results of Mail Service ACL lookups.
# Tune these to make the cache more responsive to changes in the SACL.
# The cache is only in memory, so bouncing the sacl-cache service clears it.
use_sacl_cache = yes
# sacl_cache_positive_expire_time = 7d
# sacl_cache_negative_expire_time = 1d
# sacl_cache_disabled_expire_time = 1m
#======================================================================
mydomain_fallback = localhost
message_size_limit = 104857600
biff = no
mynetworks = 127.0.0.0/8,www.yourvirtaldomain.com
smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated reject_rbl_client zen.spamhaus.org permit
recipient_delimiter = +
smtpd_tls_ciphers = medium
inet_protocols = all
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
recipient_canonical_maps = hash:/etc/postfix/system_user_maps
smtpd_use_pw_server = yes
smtpd_sasl_auth_enable = yes
content_filter = smtp-amavis:[127.0.0.1]:10024
inet_interfaces = loopback-only
smtpd_helo_required = yes
smtpd_pw_server_security_options = cram-md5,gssapi
header_checks = pcre:/etc/postfix/custom_header_checks
smtpd_tls_CAfile = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.chain.pem
smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
relayhost =
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination check_policy_service unix:private/policy permit
smtpd_enforce_tls = no
smtpd_use_tls = yes
enable_server_options = yes
smtpd_tls_key_file = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.key.pem
smtpd_tls_cert_file = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.cert.pem
mydomain = yourdomain.com
virtual_alias_maps = $virtual_maps hash:/etc/postfix/virtual_users
virus_db_update_enabled = 1
mailbox_transport = dovecot
postscreen_dnsbl_sites = zen.spamhaus.org*2
maps_rbl_domains =
virtual_alias_domains = $virtual_alias_maps hash:/etc/postfix/virtual_domains
config_directory = /Library/Server/Mail/Config/postfix

Calendar Server Migration from iplanet5.2 to Sunjava messaging server

Hi
Can any one help me on Calendar server migration.
How can i migrate the calendar server from iplanet 5.2 to sunjava messaging server
Users
Calendar resources
Groups
Attributes

Hi,
I assume you mean iplanet calendar server 5.1.1 to the latest calendar server (6.3). If so, I suggest you start by reading through the calendar server admin guide which goes through the steps involved and tools to use to migrate from 5.1.1 onto calendar server 6.3.
http://www.sun.com/bigadmin/hubs/comms/library/manuals.calendar.jsp
Regards,
Shane.

Login Error after installing Lion and migrating from time machine

I cannot log into Lion under my user setting, I am getting the error: "You are unable to login to the File Vault User account {name} at this time."
Apparently I did not turn off file vault before upgrading to Lion and when I set up Lion I did not migrate from time capsule because it was not finding it even thought the firewire was plugged in so I went ahead and filled out my name and set up a password. I was in Lion and attached the external drive and finally it read it so I migrated the information. I'm not sure if I didn't check the transfer "user" box or the Lion password does not match my File Vault password but now I cannot get into Lion.
I contacted Apple Support and they told me I would not be able to access my old user info because it is locked. I tried to reinstall Lion and get back to the screen where it prompts me for a password so I could change it to my file vault password and cannot get back to that screen. I also cannot create a new user - I can only use guest.
I tried reset password from the terminal and this did not work.
Is there any way I can do a clean Lion install and try the migration again to make sure the passwords and user box is checked?
Please help... I'm desperate!

You say Downloads folder has never been excluded and you can't find the Downloads Folder. Do this... OpenFinder then in Finder select your Downloads Folder, open Time Machine if your Downloads Folder has been backed up, Time Machine will take you directly to your Downloads Folder backups.

Sql server migration from 2005 to 2012 (110)

hi, experts,
the database of .net web form application (Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1025 ) that I am responsible will be migrated to sql server 2012 (110).
the .net webform use the functions from System.Data.SqlClient. should be ado.net
e.g.
public static DataSet LoadByID(int id)
SqlConnection conn = new SqlConnection();
DataSet ds = new DataSet();
try
conn.ConnectionString = ConfigurationManager.ConnectionStrings["connection_string"].ToString();
conn.Open();
SqlParameter[] aryParams = new SqlParameter[1];
aryParams[0] = new SqlParameter("@ID", SqlDbType.Int);
aryParams[0].Value = id;
SqlCommand cmd = new SqlCommand("a_store_procedure_name", conn);
cmd.CommandType = CommandType.StoredProcedure;
cmd.Parameters.AddRange(aryParams);
SqlDataAdapter sqlAdapter = new SqlDataAdapter(cmd);
sqlAdapter.Fill(ds);
catch (Exception ex)
throw ex;
finally
if (conn.State == ConnectionState.Open)
conn.Close();
return ds;
I cloned the database from 2005, restore into 2012 and change the compatibility level to 110 of cloned database.
I am doing tests on the sql server 2012 from the web application user interface. (changed connection string to new 2012 db)
I found that I always hit this error
any configuration for whole web form application?
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Source Error:
delaynomore.

Hi delaynomore,
According to your description, you fail to execute the function with timeout error after migration to SQL Server 2012. Based on my research, the issue could be due to the long running tasks or uncommitted transactions.
To troubleshoot the issue, besides Olaf's suggestion to check the connection to SQL Server 2012 instance and the stored procedure using SQL Server Management Studio(SSMS) manually, you could also follow the methods below.
1. Execute that procedure manually using SSMS and check if it takes a very long time to execute and return. For example, there could be millions of rows being updated. If it takes a long time, you can adjust the CommandTimeout accordingly.
2. Execute the following statement in SSMS to check if there are any uncommitted transactions: dbcc opentran ('yourDatabaseName'). If there are any uncommitted transactions, please change the stored procedure accordingly to commit the transactions.
For more information about the process, please refer to the article:
http://blogs.msdn.com/b/spike/archive/2008/07/31/timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is-not-responding.aspx
Regards,
Michelle Li

Problems getting Lion server down from App store

I have a Mac mini server runing Snowleopard server just fine. Tried upgrading to Lion via the App store - OSX 10.7.4 came down fine - but not the server extension.
I end up in a loop where OSX10.7.4 won' install because the server extension is not avilable, and can't download Liion server extensions from the App store because 10.7.4 is not installed.
Any one know how to get the server extensions down before installing Lion so the install gets going?
Cheers,
Glen

Hey Glen -
I'm not at all sure why you're getting these errors, as I've followed this upgrade path just this week; but with a difference, I upgraded a client SL Mac (not server).
I'm going to suggest this - and you may even be able to do it at your local apple store with a Genius present.
Find another Lion machine and log into the app store on the account that bought Lion. Find Lion and click the download button. It'll tell you that you purchased before and you won't be charged again - let it roll. The download will proceed and when finished, will start the installer. At that point quit the installer.
Do the same with Lion Server; download again at it's App Store page.
Come prepared with a nice fat USB Stick. Copy both Installers onto the stick. They'll be in the Applications folder on this Mac.
Go to your SL Server, which MUST be at least 10.6.8.
Copy both files to the Applications folder. If there's an old Lion installer in there, overwrite it; you just got the latest build that way.
After copying to Applications, the Server installer will be greyed out and have a disable icon across it. That's normal; it can't run on anything less than 10.7. It just needs to sit there right now.
Run the Lion installer - client, that is.
It'll restart at some point - and then, because you have copied the server installer to Applications already, it will see that you want it to be a Server upgrade and will start quizzing you a bit about your setup and roll over your existing settings where it sees them.
When it's done you'll see your familiar login screen. And yes, it's server! Even though About This Mac says its 10.7.4- it really is Server. Start the Server App (not Server Admin app) and you'll see the new interface.
Server tools for Lion is a seperate download, so trash any SL versions at this point. You can DL the new ones anytime if you have a hankering for fine tweaking, but you're pretty good right out of the gate with just Server app.
Hope this helps. I've basically quoted a lesson from the Lynda.com Lion Server tutorial. Just a satisfied customer.
Tony

Migrating FROM Gmail to 10.6 Mail server

I am in the process of setting up a new 10.6 Server to be used for internal Mail, iChat, iCal, Wiki, & File Sharing. We are currently using Gmail for all email.
Can anyone recommend the best way to move all current emails in each account on Gmail to the SL Server that I am setting up possibly in a manner that involves as little downtime as possible?
Each user (around 45 of them) with the exception of five Mac users in the company who use Mail, are all using Gmail's web interface. I have thought about installing an email client (all using win xp or vista) using IMAP and DL all emails to their computer, but this leaves the only copy of that email on that computer system, and would be a pain when their station has to be switched out for any reason to move the emails to the new system. Recommendations?
L Nail

That you're asking this question is somewhat concerning.
Depending on the tool (and in the typical case), you're transferring messages directly from one mail server to another mail server.
Actually, since this is the first Mac OS X server, and mail server at that matter, that I have set up, I do believe that this is a valid question, and shouldn't be alarming one bit. I have not yet turned on the mail server, nor have I begun to delve into all of the documentation yet, as the mail server is the last part to implement.
Presuming imapsync, you're using a tool that pretends to be a mail client to two different mail servers in parallel; it pulls down messages from one and synchronizes those messages directly to another server.
For another document on the imapsync tool, here is the [imapsync readme|http://www.linux-france.org/prj/imapsync/README] via [Freshmeat|http://freshmeat.net/projects/imapsync>
Thank you for the direction to some more documentation on imapsync!
lnail

File Server Migration from 2008 Standard to 2012 Standard accross different subnet

Hi
Im going to migrate File server from Windows 2008 Standard server to Windows 2012 Standard . Source and Destination Servers are on different subnets . According to this
http://technet.microsoft.com/en-us/library/jj863566.aspx I cannot use Server migrations tool in-built into 2012 . Im not sure if I can use file server migration toolkit 1.2?.
Also my Domain controllers are mixture of Windows 2003, 2008 , 2008 R2 and I've upgraded the schema level to 2012 R2 . Is there anything else I need to be aware of ?
Can anyone please recommended best way to go about doing this migration . Is file server migration toolkit 1.2 is compatible ? .
Only reason I don't want to use Robocopy to this is because If I miss a small setting etc then I will face unwanted downtime.
I presume Migration toolkit will also create all the Quotas etc on the destination server .
Thanks
mumtaz

Hi mumtaz,
We could use file server migration toolkit 1.2 to migrate file server between the two subnets. In order to maintain security settings after the migration, please ensure the security of files and folders after they are migrated to a target file server, the File
Server Migration Wizard applies permissions that are the same as or more restrictive than they were on the source files and folders, depending on the option you select.
In the meantime, quota cannot migrate by this tool but we can export and import the quota using dirquota command. Export the templates as xml and then import to new server:
dirquota template export /file:C:\test.xml
dirquota template import /file:C:\test.xml
For more detailed information, please see:
Template Export and Import Scenarios
http://technet.microsoft.com/en-us/library/cc730873(WS.10).aspx
Regards,
Mandy
If you have any feedback on our support, please click
here
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Lion Server Migration OK- But wiki dead

Hi,
We did an almost flawless upgrade to Lion from 10.6.8 server....
However Wiki's seem to have died...
I did a second manual migration of the wiki data... but still dead....
Help....

OK it was pretty dead.
Seems no matter what I did if web services were off Wiki's worked, but if I enabled web services the Wiki's died.
Looks like like an uncontrolled http redirect is happening.
I stripped all the conf files out of the apache2 directory and the same thing happened afterI set all the sites up again...
So I'm stuck. I rolled the server back and have left on Snow Leopard.

Migrate from OS X Wiki to Wordpress

For various reasons, we're in the process of moving our knowledge base off of OS X Leopard Server Wiki, onto Wordpress.
I know that WordPress offers RSS/XML import, but it's not working. Does anyone have a suggestion on how to make this work, or perhaps advice on migrating the data going another route?
Thanks!

I was just pondering exactly the same move. Wondering if you wouldn't mind offering some more details.
You indicate:
I was able to use Feeder, however, to import the RSS file directly from the
wiki, then save it locally and import the local file into Wordpress.
Is Feeder this? (http://reinventedsoftware.com/feeder/), or something different?
Any specifics you could provide would be appreciated.

Can someone help me with optimal specs for a 2012 R2 server migration from 2003 R2?

My specs for the Windows Server 2003 R2 which is our file server are:
Intel Core 2 CPU 6600 @ 2.40GHz (2 CPU's), ~2.4GHz Processor types are x86 Family 6 Model 15 Stepping 6 GenuineIntel ~2399 Mhz Physical Memory is 2 GB RAM Virtual Memory is 4 GB We have 6 fixed drives in place. They all range from 300 GB to 1 TB in total space.
We have two roles on the file server in place which are File Server and WINS Server. We have QuickBooks running on it and a bunch of random smaller applications as well.
When it comes to purchasing servers, we're open to either getting all the parts and building it from the ground up or a built machine. So my question is when getting Server 2012 R2, based on what I said, what hardware should I be getting? If you need more information,
please don't hesitate to ask.
Also, if you know where I could find quality documentation on the actual migration process for a file server between 2003 R2 and 2012 R2, please let me know.
Thank you for reading. ^_^

Hi,
Since Microsoft is ending support for Windows Server 2003 R2 mid-2015, there are a bunch of resources. To partially answer your question. I came across the following blog by Jose Barreto that might be able to help.
http://blogs.technet.com/b/josebda/archive/2014/11/05/migrating-file-server-from-windows-server-2003-to-windows-server-2012-r2.aspx
Thanks,
Jeff Thai
www.AvePoint.com
Please Mark Answered if my reply solves your problem. Thanks!

Calendar server Migration from one server to another

Dear folks,
We are planing to move our calendar server from one server to another, Platform is same, OS is same, Calendar server on both systems are having similar version, Only pointing to new directory server but same schema level and populated with same users,
What would be the best approach to accomplish this:
1) Just take backup of Database & Restore it on the new server
2) Run Migration utility .....
ll appreciate for any help......
Thanks

Sp00ky_Geek wrote:
We are planing to move our calendar server from one server to another, Platform is same, OS is same, Calendar server on both systems are having similar versionHow 'similar'? (showrev -p | grep ics)
Only pointing to new directory server but same schema level and populated with same users,
What would be the best approach to accomplish this:
1) Just take backup of Database & Restore it on the new server
2) Run Migration utility .....Which migration utility?
If they are the same platform/version you should be able to copy the database across as-is. The users directory entries (icsdwphost) will need to be updated to reflect the new hostname for the calendar server.
As with any move/migration, test and retest.
Regards,
Shane.

Server Migration from SLS to ML and from OD to AD

Current setup:
small network of macs (10 users, mostly ML), using a mac mini with SLS as OD server. SLS provides: OD, DNS, AFP, VPN, Time Machine
we are merging with a (somewhat) larger company that has a Windows 2003 Server (which provides AD, DNS and network folders, not much else) and windows clients.
Now I would like to:
1) move my 10 users to AD, keeping my mac server in a golden triangle setup
2) upgrade SLS to ML, since I am interested in using the Profile Manager (all users of the two companies use company provided iphones), and would like to continue to have centralized time machine backups for mac machines.
My questions:
1) what should I tackle first, upgrade to ML, then migrate users, or viceversa?
2) is golden triangle the best solution? is a trust relationship between the two domain servers an acceptable replacement?
3) what is the best way to migrate users? I would like to maintain all their settings, but do not care about having to reset passwords. all mac users are mobile users. Here is what I would do (on each mac client, once OD is joined to AD in golden triangle setup):
a. make a backup copy of home folder, then rename the home folder
b. create a new user on AD with same login name as old mac user
c. copy files from backup folder to new home folder
d. make sure all files are owned by user:DOMAIN\group
e. make sure new users belongs to same groups on joined OD as the old one, so that access to mac-server provided services remains unchanged
What happens with mobile home folders? Will the network copy remain on the mac server? Must this be set up within AD somehow?
Thanks for any help!
Chris

In both cases, you should check
Oracle® Database Upgrade Guide
11g Release 1 (11.1)
http://download.oracle.com/docs/cd/B28359_01/server.111/b28300/toc.htm
also note, Only Oracle 10.2.0.3 are supported on vista platform, make sure you download and install 10.2.0.3 for Microsoft Windows Vista before upgrade.
http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10203vista.html

Lion server migration from 10.6 wiki dead, mail dead, ical dead

Similar Messages

Maybe you are looking for