10.4.10 apparently broke my server
Hi,
Just upgraded to 10.4.10 on our school's server. It's a PowerMac G4 "Sawtooth" with, oh, about 750 MB of RAM and a RAID 1 card hooked up to two 250 GB hard drives. Otherwise stock. Computer worked fine right up until I rebooted it. Now it's stuck at the gray screen with the apple logo--no spinning gear. Verbose logging start up mode didn't work; neither did safe mode. Went into open firmware and reset-all. Also reset PRAM a few times. Started up from the install disc--that worked. Repaired permissions, repaired disk. Rebooted using the internal hard drive. Nothing. Stuck at gray screen with the apple. Pre-update back-up was already corrupted from before. What should I do now? Can I force install 10.4.whatever I have on the DVD without over-writing all the precious settings?
Okay, so apparently when you start in safe mode you have to hold down the right shift key. After successfully starting in safe mode, I get several cryptic messages, one saying that a certain driver does not support Mac 3,1. Ideas? Anyone? I have scrapped the idea of a quick recovery and am now just trying to figure out a way to move my data to another machine, to be followed up with a complete nuke and re-pave.
Similar Messages
-
URGENT PLEASE HELP: Broker only serving one queue consumer at a time
Hello all,
I have multiple consumers listening on a queue. The broker sends a message to the first listening consumer. This consumer receives that message and acknowledges it. and does some processing with it.
All other consumers do not get any message from the broker. They are all listening on the queue for a long time. After i kill the first consumer one of the listening consumer gets a message.
How can I configure the queue so that it sends multiple (different) messages to all the listening consumers with minimum delay?
I am using a persistent queue and using 3.5 sp2 on windows.
Thanks a lot in advanceSounds like your number of active consumers is set to 1 which is the default. Use imqcmd to set the maxNumActiveConsumers on your queue. The Platform Edition supports up to two active and one backup consumer. The Enterprise Edition does not have any limits.
-
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 errorhere'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 -
SECURITY UPD 2009-05 BROKE MAIL SERVER
After the update all mail gets stuck in the queue and won't be forwarded to user. Any fixes for this? Thanks
Thank you
Here is the SMTP log - (for each stuck email I have one of these)
Sep 18 16:13:55 srv1 postfix/error[970]: E063AB2210: to=<[email protected]>, relay=none, delay=23579, delays=23579/0.59/0/0, dsn=4.3.0, status=deferred (mail transport unavailable)
Here is the Postfix config file.
Last login: Fri Sep 18 15:56:29 on console
srv1:~ alpha$ postconf -n
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter =
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps =
luser_relay = admin
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 0
mydestination = $myhostname,localhost.$mydomain,localhost,alphaway.net,mail.alphaway.net,srv1.a lphaway.net
mydomain = alphaway.net
mydomain_fallback = localhost
myhostname = srv1.alphaway.net
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpsasl_authenable = yes
smtpsasl_passwordmaps = hash:/etc/postfix/sasl/passwd
smtpsasl_securityoptions =
smtpdenforcetls = no
smtpdpw_server_securityoptions = none
smtpdrecipientrestrictions = permitmynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = no
smtpdtls_certfile = /etc/certificates/Default.crt
smtpdtls_keyfile = /etc/certificates/Default.key
smtpdtlsloglevel = 0
smtpduse_pwserver = no
smtpdusetls = no
unknownlocal_recipient_rejectcode = 550 -
Any help will be appreciated. I upgraded to 4.3.3 and it apparently broke the password authentication for my work exchange account. I can't get my iCal on my desktop after Lion and now this. Grrr. It continues to hit the server and locks me out so I can't get email from any computer. Does anyone have a fix? If not can I restore the previous version? It was working perfect.
Thanks in advance.As far as I know, it is not possible to downgrade to a previous iOS. Apple doesn't support it.
-
Server 2012R2 -- RDS Farm with XP and Windows Vista Clients
Hi There,
My team has been having some fun in getting our Server 2012R2 farm operational, annoyingly MS documentation is severely lacking on how to correctly configure a 2012R2 Farm correctly.
We have an RDG1-TCC server, which is the RDGateway, RDConnection Broker and RDWeb Server. We have two session host servers RDS1-TCC and RDS2-TCC.
It took us some time and much online research to figure out exactly how we needed to configure the RDS server as a lot of information online for 2012R2 was apparently incorrect(was based on 2008R2 practices). We started off with using a DNS Round Robin for
the RDS Session hosts servers and after a number of certificate issues, we later found this was incorrect. We're now using RDWeb exclusively, which appears to be the correct way to have the Connection Broker working?
We've ran into a number of issues with certificates too, we have an external certificate for remote.domain.com. Installing this on all 4 options in the certificate manager has made internally work correctly via RDWeb, however externally we are getting a
certificate mismatch as it's trying to connected to RDG1-TCC with a certificate for remote.domain.com. I'm pretty sure I can resolve this with a replacement remote.domain.com certificate that includes a SAN for *.domain.internal. Testing with a self signed
certificate seemed to resolve this issue.
Now providing i've configured everything the correct way, we have an issue where RDWEb RDP files do not work internally or externally for XP, Vista or Windows 7 (With RDP7.1). Windows 8/8.1 and Windows 7 with RDP 8/8.1 updates work perfectly fine. Unfortunately
this new client has a few XP machines that they are not willing to update just yet.
Is there a known fix/workaround to get these older clients working correctly?
Sorry for the extremely long post, but I'm sick of banging my head against the wall trying to get something that we assumed would have been fairly simple to get up and running.
Cheers,
BenThanks for the assistance so fat, now I have all clients connecting, I need to tackle the certificate issues.
The UC SAN certificate is going to cost much more than the current certificate, currently that idea is on the back burner as the client does not wish to pay a few hundred extra.
To quickly sum things up:
AD DNS(internal DNS) override in place for remote.domain.com.au pointing it to the internal IP of the gateway/connection broker/RDWeb server.
Connecting Internally its working perfectly fine under all circumstances (I'm guessing this is because of Kerberos Auth)
When users connect externally via RDWeb they get a certificate missmatch as the cert is for remote.domain.com.au and the server is RDG1-TCC.domain.com.net
When users connect externally via MSTSC using the Gateway option, they get a certificate missmatch as per the above, however they also receive a second "certificate is not trusted" error for whatever RDS server they hit.
I have tried the below previously and they broke other things:
"Change published FQDN for Server 2012 or 2012 R2 RDS Deployment."
This resolved the external certificate issue. However then internal connections stopped working. When connecting via RDWeb, you would get asked for credentials instantly and no matter what you entered, it just asked for credentials again.
There did not seem to be ANY event logs for this connection.
"Changing RDP-Tcp listener on RDSH to use external certificate."
I can't recall the exact error we had when we did this, but I know we had to roll back the change. I have a feeling we then started getting certificate missmatch errors on the Session Hosts.
I'm half thinking that when the farm is free(Currently being used for application UAT), I'm going to try and reconfigure the RDP-Tcp listener on the RDSH servers again and see if that resolves one or more of our issues.
Do you have any suggestions on how I can use the correct published FQDN name without breaking internal access? Or any other ideas on getting this entire thing working both internally and externally?
Also, Dharmesh, I've tried clearing out the certificate cache as suggested, but to no avail. -
Moving user profiles from Server 2012 with RDS services to User profile disks Server 2012R2
Hello i have a question about moving my C:\users profiles.
My current settings on the servers are:
AD-Server 2012
SQL-Server 2012
TS- server with RDS roles (RDwebacces, RDs broker, RD session host) 2012
everything about user profiles is now in C:\Users
My new settings for the server will be:
AD-ActiveDirectory - server
SQL-Server
TS1- RDS (RDwebacces, broker, RDS server group management) 2012R2 (I have enabeld userProfileDisks to Filesistem server)
TS2- RDS(Session host) load balance 2012R2
TS3- RDS (Session host) load balance 2012
FileSistem - server ( here i will have on E: partition the new functionality UserProfileDisks) 2012R2
So is there a way to move profiles from TS - C:\Users to FileSistem - E:\UserProfileDisks
I am new to this so any idea wil be helpful.Hi,
If the UPD is configured on the server which holds existing user profiles, just select the option:
store all user settings and data inside the profile disk.
Since you are moving user profiles between different servers, then user profile contents need to be migrated manually.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
We recently switched hardware and server software Win SBS 2008 to 2012R2 for a small network roughly 40 clients (Win7 Pro / Win 8.1 Pro) about 16 running concurrently at a given time and one network printer with the printer queue residing on the DC as well.
I read that a single server environment might not be ideal in particular no fail-over but that is an accepted risk in this particular network here.
Errors:
Error 1043: Timeout during name resolution request
Error 1129: Group policy updates could not be processed due to DC not available
Error 5719: Could not establish secure connection to DC, DC not available
Occasionally but disappears after a while
Error 134: As a result of a DNS resolution timeout could not reach time server
Symptoms
On Win 7 Clients
Network shares added through Group Policy will not show sometimes
Network shares disconnect (red X) and when accessed return access authorization error after one or two clicks on the share finally grant access again
When the issue with accessing network shares occurs, it usually also affects Internet access meaning a 'server not responding' error appears in the browser windows when trying to open just any web page
nslookup during the incident returns cannot resolve error
ipconfig on client shows correct default router (VDSL Router) and DHCP / DNS Domain Controller
Also, the Win system log shows the above errors during these incidents, however, the nuimber of incidents vary from 20-30
On Win 8.1 Clients
Same as above with the slight variation for network shares apparently due to Server 2012 and Win 8.1 clients managing drive shares differently. However, network share refresh does not work with this clients. In most cases only a gpupdate /force returns
drive shares but usually only for the active session. After logoff / logon the shares are gone again.
The issue does appear to be load related since it occurs even if there are only one or two workstations active.
Server Configuration
Dell R320 PowerEdge 16GB / 4TB 7200RPM RAID10 / GBitEthernet
Zyxel 1910-48 Port Switch
VDSL 50Mbps Down / 20Mbps Up
Since the DC is the only local DNS and there are no plans to add another one or move DNS to another server, the DNS server is configured with this own address as preferred DNS with three DNS forwarders 1) VDSL Router 2) ISP DNS1 3) ISP DNS2
Currently only one Network card is active for problem determination reasons.
There appears to be no consensus concerning IPV6 enabled or disabled, I tried both with no apparent effect
I have set all network cards server and client to Full Duplex and the same speed, also disabled Offload functions within the adapter settings. Some but no consistent improvements.
Best Practice Analyzer Results
DNS server scavening not enabled
Root hint server XYZ must respond to NS queries for the root zone
More than one forwarding server should be configured (although 3 are configured)
NIC1 should be configured to use both a preferred and alternate DNS (there is only one DNS in this network)
I have found some instructions to apply changes to the clients through a host file but I would rather like to understand whether this DNS response time issue can be resolved on the server for example timing setting perhaps. Currently the DNS forwarders are
set to 3 second.
Since a few people have reported issues with DNS but most are working with multi DNS, DC environment I could not really apply any suggestions made there. perhaps there is anyone like me who is running a single server who has overcome or experience the same
issues. Any help would be appreciatedHello Milos thx for your reply.. my comments below
1. What does it "switched"? You may mean migration or new installation. We do not know...
>> Switched is probably the incorrect term, replaced would be the appropriate wording. Before, there was a HP Proliant Server with SBS 2008 with distinct domain and now there is a Dell Server with MS 2012 R2 with a distinct domain. Client were
removed from one (SBS) domain and added to the new Server 2012 domain. Other components did not change for example same Network Switch or VDSL Router, Workstations and Printer
2. Two DCs are better alternative. Or backup very frequently. There are two groups of administrators. Those who have lost DC and those who will experience this disaster in near future.
>> Correct, and I am aware of that
3. NIC settings in W 7 and W 8.1, namely DNS points to DC (...and NOTHING else. No public IP or that of router DNS.))
>> Correct, this is how it's currently implemented. Clients point to DC for DHCP and DNS and Default Router, no public IP or DNS. The only references to ISP DNS exist on the VDSL Router itself as provided through ISP when establishing VDSL
Link and the list of Forwarders in the DNS Server configuration. However, I have just recently added the ISPs DNS as forwarders for test purposes and will probably learn tomorrow morning whether this had any effect for better or worse.
4. Do nslookup to RR on clients. RR branch is saying client basic info on LDAP parameters of AD.
>> Will post as soon as available
5. I do not use forwarders and the system works
>> Ok, does this mean it works for you in a similar or the same infrastructure setup or are you saying it is not required at all and I can remove any forwarder in a scenario like mine? If not required can you explain a bit more why it is not
required apart from that it does work for you that way?
6. DHCP should sit on DC (DHCP on router is disabled)
>> Correct, no other device is configured to provide DHCP service other than DC and DHCP is currently running on DC
7. NIC settings in DC points to itself (loopback address 127.0.0.1)
>> Are you sure this is still correct and does apply to Server 2012? I am reading articles stating that it should be the servers own IP but local loop or should this be added as alternate DNS in addition to the servers own IP?
8. Use IPCONFIG /FLUSHDNS whenever you change DNS settings.
>> OK, that was not done every time I changed some settings but I can do that next week. Reboot alone would not suffice, correct?
9. Test your system with dcdiag.
>> See result below
10. Share your findings.
Regards
Milos
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = GSERVER2
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\GSERVER2
Starting test: Connectivity
......................... GSERVER2 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\GSERVER2
Starting test: Advertising
......................... GSERVER2 passed test Advertising
Starting test: FrsEvent
......................... GSERVER2 passed test FrsEvent
Starting test: DFSREvent
......................... GSERVER2 passed test DFSREvent
Starting test: SysVolCheck
......................... GSERVER2 passed test SysVolCheck
Starting test: KccEvent
......................... GSERVER2 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... GSERVER2 passed test
KnowsOfRoleHolders
Starting test: MachineAccount
......................... GSERVER2 passed test MachineAccount
Starting test: NCSecDesc
......................... GSERVER2 passed test NCSecDesc
Starting test: NetLogons
......................... GSERVER2 passed test NetLogons
Starting test: ObjectsReplicated
......................... GSERVER2 passed test
ObjectsReplicated
Starting test: Replications
......................... GSERVER2 passed test Replications
Starting test: RidManager
......................... GSERVER2 passed test RidManager
Starting test: Services
......................... GSERVER2 passed test Services
Starting test: SystemLog
......................... GSERVER2 passed test SystemLog
Starting test: VerifyReferences
......................... GSERVER2 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : GS2
Starting test: CheckSDRefDom
......................... GS2 passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... GS2 passed test CrossRefValidation
Running enterprise tests on : GS2.intra
Starting test: LocatorCheck
......................... GS2.intra passed test LocatorCheck
Starting test: Intersite
......................... GS2.intra passed test Intersite
Server: gserver2.g2.intra
Address: 192.168.240.6
*** gserver2.g2.intra can't find g2: Non-existent domain
> gserver2
Server: gserver2.g2.intra
Address: 192.168.240.6
g2.intra
primary name server = gserver2.g2.intra
responsible mail addr = hostmaster.g2.intra
serial = 443
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
> wikipedia.org
Server: gserver2.g2.intra
Address: 192.168.240.6
Non-authoritative answer:
wikipedia.org MX preference = 10, mail exchanger = polonium.wikimedia.org
wikipedia.org MX preference = 50, mail exchanger = lead.wikimedia.org
polonium.wikimedia.org internet address = 208.80.154.90
polonium.wikimedia.org AAAA IPv6 address = 2620:0:861:3:208:80:154:90
lead.wikimedia.org internet address = 208.80.154.89
lead.wikimedia.org AAAA IPv6 address = 2620:0:861:3:208:80:154:89
Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)
192.168.240. 6 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0,001 | 0,002 | 0,003 | 0,001 | 100,0 |
+ Uncached Name | 0,027 | 0,076 | 0,298 | 0,069 | 100,0 |
+ DotCom Lookup | 0,041 | 0,048 | 0,079 | 0,009 | 100,0 |
---<-------->---+-------+-------+-------+-------+-------+
gserver2.g2.intra
Local Network Nameserver
195.186. 4.162 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0,022 | 0,023 | 0,025 | 0,000 | 100,0 |
- Uncached Name | 0,025 | 0,071 | 0,274 | 0,065 | 100,0 |
- DotCom Lookup | 0,039 | 0,040 | 0,043 | 0,001 | 100,0 |
---<-------->---+-------+-------+-------+-------+-------+
cns8.bluewin.ch
BLUEWIN-AS Swisscom (Schweiz) AG,CH
195.186. 1.162 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0,022 | 0,023 | 0,026 | 0,001 | 100,0 |
- Uncached Name | 0,025 | 0,072 | 0,299 | 0,066 | 100,0 |
- DotCom Lookup | 0,039 | 0,042 | 0,049 | 0,003 | 100,0 |
---<-------->---+-------+-------+-------+-------+-------+
cns7.bluewin.ch
BLUEWIN-AS Swisscom (Schweiz) AG,CH
8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0,033 | 0,040 | 0,079 | 0,011 | 100,0 |
- Uncached Name | 0,042 | 0,113 | 0,482 | 0,097 | 100,0 |
- DotCom Lookup | 0,049 | 0,079 | 0,192 | 0,039 | 100,0 |
---<-------->---+-------+-------+-------+-------+-------+
google-public-dns-a.google.com
GOOGLE - Google Inc.,US
UTC: 2014-11-03, from 14:33:12 to 14:33:29, for 00:17,648
15: 40
192.168.240. 6 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0,001 | 0,002 | 0,004 | 0,000 | 100,0 |
+ Uncached Name | 0,025 | 0,074 | 0,266 | 0,063 | 100,0 |
+ DotCom Lookup | 0,042 | 0,048 | 0,075 | 0,007 | 100,0 |
---<-------->---+-------+-------+-------+-------+-------+
gserver2.g2.intra
Local Network Nameserver
195.186. 1.162 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0,022 | 0,024 | 0,029 | 0,001 | 100,0 |
- Uncached Name | 0,024 | 0,073 | 0,289 | 0,067 | 100,0 |
- DotCom Lookup | 0,039 | 0,041 | 0,043 | 0,001 | 100,0 |
---<-------->---+-------+-------+-------+-------+-------+
cns7.bluewin.ch
BLUEWIN-AS Swisscom (Schweiz) AG,CH
195.186. 4.162 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0,022 | 0,024 | 0,029 | 0,001 | 100,0 |
- Uncached Name | 0,025 | 0,073 | 0,286 | 0,065 | 100,0 |
- DotCom Lookup | 0,041 | 0,066 | 0,180 | 0,037 | 100,0 |
---<-------->---+-------+-------+-------+-------+-------+
cns8.bluewin.ch
BLUEWIN-AS Swisscom (Schweiz) AG,CH
8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0,033 | 0,038 | 0,077 | 0,009 | 100,0 |
- Uncached Name | 0,042 | 0,105 | 0,398 | 0,091 | 100,0 |
- DotCom Lookup | 0,049 | 0,066 | 0,141 | 0,025 | 100,0 |
---<-------->---+-------+-------+-------+-------+-------+
google-public-dns-a.google.com
GOOGLE - Google Inc.,US
UTC: 2014-11-03, from 14:39:59 to 14:40:12, for 00:13,363 -
Event ID: 1280 Server 2012 RDS - web app fail on second session host
Hello there
Topography
SBS 2011 (domain controller)
Two VM’s:
VM1 – All RDS rolls: RD Gateway , Connection broker, Licensing and RD access installed and acting as a session host with an active collection for RD web apps. A CA trusted certificate is installed.
VM2 – Session host with a second collection for RD web apps
Problem
I have a single app installed on both session hosts (the apps require their own servers). Both appear on the RDWeb site available for use. I can run the app hosted on VM1 no problem, but when I try to open the second app hosted on VM2 I get
two issues:
An error is returned
“Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address and the certificate subject name do not match. Contact your network administrator for assistance".
When viewing the certificate, it actually shows the CA cert installed on the
SBS server for RWW, not the cert on VM1. This has me puzzled
Secondly on VM 2, I get
Event ID: 1280 Warning Microsoft Windows TerminalServcies-session broker client
Remote Desktop Services failed to join the Connection Broker on server sever-vm1.local.
Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.
When I run the app internally it seems to load but then disappears.
Some further config info if it is relevant:
I have port 4043 (443 used) as the only port directed to the gateway
Am I missing something simple? DNS? Port forwarding issue on the router? Its my first deployment of this nature with RDS 2012
Regards
MIS5000Hi,
Thank you for posting in Windows Server Forum.
Firstly please check the RDP version you are using. I suggest you to update to RDP 8.1 for better feature and functionality. Now other thing verify that you have the RD Gateway certificate name matches the external FQDN of the RD Gateway Server. Also please
check that certificate is added under local computer\personal store and must be signed by trusted root authority.
Please check below article for more detail.
TS Gateway Certificates Part III: Connection Time Issues related to TS Gateway Certificates
http://blogs.msdn.com/b/rds/archive/2008/12/18/ts-gateway-certificates-part-iii-connection-time-issues-related-to-ts-gateway-certificates.aspx
In regards to resolve other issue (Event ID 1280), identify and fix any connectivity problems between the RD Session Host server and the RD Connection Broker by doing the following:
• Check network connectivity to the RD Connection Broker.
• Start the Remote Desktop Connection Broker service.
• Add the RD Session Host server to the Session Broker Computers group.
More information.
Event ID 1280 — RD Connection Broker Communication
http://technet.microsoft.com/en-us/library/ee890889(v=ws.10).aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support -
Terminalserver Session Broker not reconnecting to existing session
Hi!
Following scenario:
Terminalserver-Farm
2x RemoteDesktopServer (Windows Server 2008R2)
1x TS Session Broker (Windows Server 2008)
A user connects to TS-Farm -> occasionally it happens that he is redirected to (for example) TS2, even if he has an active session on TS1. There is no error message displayed on the client. Subsequently he has 2 sessions, allthough the setting on the Session
Broker is set to "allow only 1 session per user". Interestingly this happens to 2 users only - both are the only ones working on Windows 8 clients (other users are on Win7).
Any ideas how to track down the problem? I don't see the correlation with Windows 8 clients at all.
Best Regards,
StefanHi!
Affected are ThinClients with RDP 5.2 - it's still working on one of the 2008R2, not on the 2nd.
I used network monitor to see traffic from an XP-Thin Client to both Terminalservers. I can see (but not understand): "T125:Disconnect Provider Ultimatum, rn-user-requested" in line 27 at the non-working Terminalserver
Client -> TS 2008R2 with working RDP:
3 11:57:33 08.01.2014 5.3233299 10.5.4.173 10.5.0.106 TCP TCP:Flags=......S., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904019, Ack=0, Win=65535 ( ) = 65535 {TCP:2, IPv4:1}
4 11:57:33 08.01.2014 5.3238252 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A..S., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063055863, Ack=2968904020, Win=8192 ( Scale factor not supported ) = 8192 {TCP:2, IPv4:1}
5 11:57:33 08.01.2014 5.3242143 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904020, Ack=2063055864, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
6 11:57:33 08.01.2014 5.3255958 10.5.4.173 10.5.0.106 X224 X224:Connection Request {ISOTS:3, TCP:2, IPv4:1}
7 11:57:33 08.01.2014 5.3273352 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063055864, Ack=2968904031, Win=64240 (scale factor 0x0) = 64240 {TCP:2, IPv4:1}
8 11:57:33 08.01.2014 5.3274171 10.5.0.106 10.5.4.173 X224 X224:Connection Confirm {ISOTS:3, TCP:2, IPv4:1}
9 11:57:33 08.01.2014 5.3293456 10.5.4.173 10.5.0.106 T125 T125:MCSConnect Initial {T125:4, ISOTS:3, TCP:2, IPv4:1}
10 11:57:33 08.01.2014 5.3298119 10.5.0.106 10.5.4.173 T125 T125:MCSConnect Response {T125:4, ISOTS:3, TCP:2, IPv4:1}
11 11:57:33 08.01.2014 5.3315607 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904443, Ack=2063057917, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
12 11:57:33 08.01.2014 5.3322727 10.5.4.173 10.5.0.106 T125 T125:Erect Domain Request, SubHeight = 0, SubInterval = 0 {T125:4, ISOTS:3, TCP:2, IPv4:1}
13 11:57:33 08.01.2014 5.3324046 10.5.4.173 10.5.0.106 T125 T125:Attach User Request {T125:4, ISOTS:3, TCP:2, IPv4:1}
14 11:57:33 08.01.2014 5.3324212 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063057917, Ack=2968904463, Win=63808 (scale factor 0x0) = 63808 {TCP:2, IPv4:1}
15 11:57:33 08.01.2014 5.3324293 10.5.0.106 10.5.4.173 T125 T125:Attach User Confirm, Result = rt-successful, Indicator = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
16 11:57:33 08.01.2014 5.3330774 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
17 11:57:33 08.01.2014 5.3331055 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1007, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
18 11:57:33 08.01.2014 5.3340565 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3eb {T125:4, ISOTS:3, TCP:2, IPv4:1}
19 11:57:33 08.01.2014 5.3340826 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1003, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
20 11:57:33 08.01.2014 5.3345604 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ec {T125:4, ISOTS:3, TCP:2, IPv4:1}
21 11:57:33 08.01.2014 5.3345856 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1004, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
22 11:57:33 08.01.2014 5.3356991 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ed {T125:4, ISOTS:3, TCP:2, IPv4:1}
23 11:57:33 08.01.2014 5.3357256 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1005, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
24 11:57:33 08.01.2014 5.3362559 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ee {T125:4, ISOTS:3, TCP:2, IPv4:1}
25 11:57:33 08.01.2014 5.3362827 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1006, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
26 11:57:33 08.01.2014 5.3450865 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR: {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
27 11:57:33 08.01.2014 5.3456510 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR:TsClientSecurityExchangePDU Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
28 11:57:33 08.01.2014 5.3456706 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063058003, Ack=2968904946, Win=63325 (scale factor 0x0) = 63325 {TCP:2, IPv4:1}
29 11:57:33 08.01.2014 5.3460200 10.5.0.106 10.5.4.173 RDPELE RDPELE:Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
30 11:57:33 08.01.2014 5.3900913 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
31 11:57:33 08.01.2014 5.3909177 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904946, Ack=2063058498, Win=64954 (scale factor 0x0) = 64954 {TCP:2, IPv4:1}
32 11:57:33 08.01.2014 5.4047118 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
33 11:57:33 08.01.2014 5.4047805 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
34 11:57:33 08.01.2014 5.4047946 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
Client -> TS 2008R2 with non-working RDP:
3 11:21:03 08.01.2014 4.7063150 10.5.4.173 10.5.0.144 TCP TCP:Flags=......S., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459527613, Ack=0, Win=65535 ( ) = 65535 {TCP:2, IPv4:1}
4 11:21:03 08.01.2014 4.7067575 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A..S., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589137033, Ack=459527614, Win=8192 ( Scale factor not supported ) = 8192 {TCP:2, IPv4:1}
5 11:21:03 08.01.2014 4.7071555 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459527614, Ack=2589137034, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
6 11:21:03 08.01.2014 4.7101168 10.5.4.173 10.5.0.144 X224 X224:Connection Request {ISOTS:3, TCP:2, IPv4:1}
7 11:21:03 08.01.2014 4.7101591 10.5.0.144 10.5.4.173 X224 X224:Connection Confirm {ISOTS:3, TCP:2, IPv4:1}
8 11:21:03 08.01.2014 4.7110721 10.5.4.173 10.5.0.144 T125 T125:MCSConnect Initial {T125:4, ISOTS:3, TCP:2, IPv4:1}
9 11:21:03 08.01.2014 4.7114117 10.5.0.144 10.5.4.173 T125 T125:MCSConnect Response {T125:4, ISOTS:3, TCP:2, IPv4:1}
10 11:21:03 08.01.2014 4.7130978 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528060, Ack=2589139965, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
11 11:21:03 08.01.2014 4.7131136 10.5.0.144 10.5.4.173 TCP TCP:[Continuation to #9]Flags=...AP..., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=2286, Seq=2589139965 - 2589142251, Ack=459528060, Win=63828 (scale factor 0x0) = 63828 {TCP:2, IPv4:1}
12 11:21:03 08.01.2014 4.7137283 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528060, Ack=2589141425, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
13 11:21:03 08.01.2014 4.7142557 10.5.4.173 10.5.0.144 T125 T125:Erect Domain Request, SubHeight = 0, SubInterval = 0 {T125:4, ISOTS:3, TCP:2, IPv4:1}
14 11:21:03 08.01.2014 4.7143931 10.5.4.173 10.5.0.144 T125 T125:Attach User Request {T125:4, ISOTS:3, TCP:2, IPv4:1}
15 11:21:03 08.01.2014 4.7144101 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142251, Ack=459528080, Win=63808 (scale factor 0x0) = 63808 {TCP:2, IPv4:1}
16 11:21:03 08.01.2014 4.7144276 10.5.0.144 10.5.4.173 T125 T125:Attach User Confirm, Result = rt-successful, Indicator = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
17 11:21:03 08.01.2014 4.7152352 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
18 11:21:03 08.01.2014 4.7152672 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1007, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
19 11:21:03 08.01.2014 4.7162762 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3eb {T125:4, ISOTS:3, TCP:2, IPv4:1}
20 11:21:03 08.01.2014 4.7163087 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1003, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
21 11:21:03 08.01.2014 4.7172413 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ec {T125:4, ISOTS:3, TCP:2, IPv4:1}
22 11:21:03 08.01.2014 4.7172699 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1004, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
23 11:21:03 08.01.2014 4.7183019 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ed {T125:4, ISOTS:3, TCP:2, IPv4:1}
24 11:21:03 08.01.2014 4.7183348 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1005, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
25 11:21:03 08.01.2014 4.7193451 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ee {T125:4, ISOTS:3, TCP:2, IPv4:1}
26 11:21:03 08.01.2014 4.7193736 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1006, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
27 11:21:03 08.01.2014 4.7234596 10.5.4.173 10.5.0.144 T125 T125:Disconnect Provider Ultimatum, rn-user-requested {T125:4, ISOTS:3, TCP:2, IPv4:1}
28 11:21:03 08.01.2014 4.7237173 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...F, SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528149, Ack=2589142337, Win=64623 (scale factor 0x0) = 64623 {TCP:2, IPv4:1}
29 11:21:03 08.01.2014 4.7237356 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142337, Ack=459528150, Win=63739 (scale factor 0x0) = 63739 {TCP:2, IPv4:1}
30 11:21:03 08.01.2014 4.7237527 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A.R.., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142337, Ack=459528150, Win=0 (scale factor 0x0) = 0 {TCP:2, IPv4:1} -
Manager Cannot Connect to Server **INTERMITTENT**
I need some help here as my OVM Manager is acting very, very funny. My system, two servers with HA enabled, was running just fine for many months. Recently I needed to do some work in the manager and both of my servers are no longer reachable. When I go to re-add the servers to the server pool and run the test connection I get different message almost every time. Sometimes it says it connects. Sometimes it says the agent isn't available. Another thing that was strange, all but one of the VMs was listed as unknown status. I can start them, stop them, etc., but I can't create new ones as the server pool is inactive, blah, blah.
I ran some tests by disabling iptables on the manager and server as well as disabled selinux, but still no go. I can ping the servers just fine.
Any thoughts on how I can debug what's going on?
FYI, I deleted the server pool (forced) and I can no longer create it since the servers are mostly not reachable.Apparently my manager server was upgraded to 2.2.1, but my VM servers weren't, thus the disconnect. The only problem is even though all of my servers are fully upgraded I cannot create the server pool. The connection tests work fine, but when I click Next to create the pool I get the following error:
OVM-3006 The Oracle VM Agent version is low and does not support the feature: Precheck High Availability.
Since the version is the latest, why is this message appearing?!! ;-) -
Options to change jdbc adapter for multiple server nodes without flag in db
Due to load, we are about to add a new server node for additional J2EE memory within XI. Reading the notes and discussions about this, it is apparent that the server nodes don't distinguish between themselves in terms of polling. i.e. If we have a jdbc channel that polls every 24 hours, and you have 2 server nodes, it polls twice at the approximate same time every 24 hours.
Question I have is how have people got around this issue where you cannot update the information to say that the data has been read. i.e. Our scenario is reading the complete table contents every day and sending all information to another system.
Hence, if we have 2 server nodes, we will execute this message twice. When we add a 3rd server node, we will have 3 messages sent at the same time per day.
One complicated option (I think) is to use an application client on XI to schedule a job which calls an ABAP Proxy on the integration client which starts off a ccBPM which in turn reads the database hence single threading this process.
Anyone got any sensible ideas?
Regards,
Matt
ps. Ignore the obvious design flaws with this approach as there is no other option in this scenario due to restrictions in the end system.Hi Matt,
Extending Bhavesh's point, and assuming the receiver system is SAP, then why not schedule your calls on the receiver system, as the consumer of the data.
The report name and optionally a date range can be written from the RFC via XI to a separate table in the database. The select statement can join the table to the existing view. The update statement can update the new table as your source table or view is obviously out of bounds.
The advantage of this approach is that it results in a classic request response where XI is transparent.
We are planning to do something very similar in our own project.
Best Regards,
Bill -
How to enable IRM licensing in exchange server 2010?
I need to enable that service but I cannot find it in the management console.
Bharat: Having difficulty with getting the perms correct, apparently:
RMS on Server 2008R2, Exchange2010, EXCHServers group has Read/Execute perms on servercertification.asmx and the inheritable checkbox is set.
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Set-IRMConfiguration -InternalLicensingEnabled $true
No connection could be made because the target machine actively refused it 192.168.1.46:443 ---> Unable to connect to t
he remote server ---> Failed to get Server Info from
https://rms.baupost.com/_wmcs/certification/server.asmx.
+ CategoryInfo : InvalidOperation: (:) [Set-IRMConfiguration], Exception
+ FullyQualifiedErrorId : 8E3210B2,Microsoft.Exchange.Management.RightsManagement.SetIRMConfiguration
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Test-IRMConfiguration
cmdlet Test-IRMConfiguration at command pipeline position 1
Supply values for the following parameters:
Sender: ************
Results : Checking Exchange Server ...
- Exchange Server is running in Enterprise.
Loading IRM configuration ...
- IRM configuration loaded successfully.
Retrieving RMS Certification Uri ...
- RMS Certification Uri:
https://rms.baupost.com/_wmcs/certification.
Verifying RMS version for
https://rms.baupost.com/_wmcs/certification ...
- Warning! Failed to verify RMS Version. IRM features require AD RMS on Windows Server 2008 SP2 with the
Hotfixes specified in Knowledge Base article 973247 (http://support.microsoft.com/kb/973247) or RMS on Window
s Server 2008 R2.
Microsoft.Exchange.Security.RightsManagement.RightsManagementException: Failed to get Server Info from https:
//rms.baupost.com/_wmcs/certification/server.asmx. ---> System.Net.WebException: Unable to connect to the rem
ote server ---> System.Net.Sockets.SocketException:
No connection could be made because the target machine ac
tively refused it 192.168.1.46:443
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& soc
ket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& except
ion)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.Exchange.Security.RightsManagement.SOAP.Server.ServerWS.GetServerInfo(ServerInfoRequest[] req
uests)
at Microsoft.Exchange.Security.RightsManagement.ServerWSManager.ValidateServiceVersion(String featureXPath
--- End of inner exception stack trace ---
at Microsoft.Exchange.Security.RightsManagement.ServerWSManager.ValidateServiceVersion(String featureXPath
at Microsoft.Exchange.Management.RightsManagement.IRMConfigurationValidator.ValidateRmsVersion(Uri uri, Se
rviceType serviceType)
at Microsoft.Exchange.Management.RightsManagement.IRMConfigurationValidator.TryGetRacAndClc() -
Is it safe to co-locate WSUS on a Remote Desk License Server / Connection Broker?
This is from the release notes on WSUS 3.0:
WSUS 3.0 is not supported on servers running Terminal Services
Although WSUS 3.0 may still run on servers running Terminal Services, doing so is not supported or recommended. WSUS 3.0 will not run on a server running Terminal Services in configurations
using remote SQL Server implementations. Because all remote custom actions (including installation) on a Terminal Server license server will be run as the system account, and the server's system account may not have permissions on the remote SQL Server, the
installation may fail.
I know it's not supported to install WSUS on a server with the RDSH role but this is server is only acting as a License Server and Connection Broker. Session Host role is not installed. I'll also be using the internal Windows Database so I don't'
think the remote SQL server issues apply here.Avoid unsupported configuration. No one will help you if you use unsupported system.
Try to use another way how to install WSUS. Consider virtualization.
Regards
Milos
I'm not sure that it would be unsupported. Terminal Services is a very broad term. I'm thinking that they don't want you to install it on a server that acts as a terminal server or RDSH. The server in question is only a broker/licensing server. -
Reports6i: Server job queue API package
Hi,
Has anyone tried editing the reports server job queue API (rw_server.clean_up_queue)? I don't want the queue table (RW_SERVER_QUEUE) to be truncated each time the server is shutdown and re-started.
(By the way, it's mentioned in the Publishing Reports manual that we can edit the API package to override the default behaviour)
I did the following:
1. I commented the truncation commands in the rw_server.clean_up_queue function
2. Stop and re-start the server.
3. The reports server inserts duplicate records for scheduled jobs.
Apparently, Oracle Reports server component stores job queue information somewhere on the hard disk(c:\orant\reports60\server) and re-inserts that info. to the database table on queue startup without checking for duplicate job_ids.
I would appreciate if someone could try this and confirm it. Is this a bug?
Thanks
ManishYou can trace the report on the reports server. This link talks about tracing from reports builder but also has links and examples of how to set up tracing on the reports server.
Maybe you are looking for
-
Which programming is used in SAP HANA? confused b/w ABAp or java?
Can anyone just tell me As a programmer in which language i have to work on SAp HANA
-
Trying to tether a Canon 60D to two copies of Lightroom 4 on two different computers
I have a Canon 60D tethered to an Imac with Lightroom 4 and also have Lightroom 4 on a Powermac. When I try to veiw imported images lightroom says it can't do a automatic import over the network. The images are captured every 3 minutes, and I need th
-
How to join tables from different databases (DBLink/DB connection )
Hello, i have an issue and i hope you could help me to solve it. My problem is: I want to create native sql select which joins two tables from different DB (both of them are ORACLE, one of them internal, another one - external). I have found several
-
How to package an obfuscated swf ?
I'm not sure how the packager works but it seems to create a new release build and then package it. Then, how can I package my own swf file after having it obfuscated ? There is no way to just browse for the swf file I want to have included. Thanks i
-
Générer un rapport independant par sous sequence dans une sequence
Bonjour, j'utilise des sequences teststand (v3.0) qui génèrent des rapport très importants. Cela donne des resultats pas lisibles, et dans le cas ou je choisit le format xml pour le rapport un message d'erreur de type out of memory venant de TestStan