Hardware for an iCal Server?

Ok this might turn into a bragging contest but mostly I'm looking into an idea of what sort of computing power we need to run our iCal server.
Currently it's this:
Mac Mini 1.5GHz Intel Core Solo
2GB RAM
OS X 10.5.4 Server w 10 clients
I have 52 users (iCal/Sunbird) currently (but only 6 connect at the moment) and want enough oomph to expand to as many as 75 users.
Right now the CPU gets pinned with Python taking up around 90% of the processing time at around 6 users. Initially the problem was that everyone (well, about 10 Mac users) attempted to sign on at once and the iCal clients all timed out since the server couldn't respond within 120 seconds. So we scaled back and overnight the 3 users who left their computers on and the 3 more whom I added one by one were able to get their Calendars synced. Going to 8 or more users however and clients start timing out again on a regular basis.
While I'm looking into an upgrade for the Mini to either a 2.0GHz, 2.16GHz, or 2.33GHz Core 2 Duo CPU (which I'll have to use a tool to manually set the fans to cool it off), I'm thinking this will likely still not be enough processing power.
An XServe (2x2.8GHz Quad Core w 2GB RAM and Unlimited Client Server - $3100) seems like overkill (I've been told I can purchase something new if necessary) and we do have a spare PowerPC G5 Dual 1.8GHz Mac which could also work. I'd prefer to not purchase an iMac (which was suggested) or a Mac Pro (slightly cheaper) if at all avoidable.
Message was edited by: Dan Brown8

I would suggest troubleshooting the CPU getting pinned as a support issue. We run a Core Duo (solo) 2GhZ iMac in a similar environment with no problems. Are you authenticating locally, or connecting to another directory?

Similar Messages

Different hardware for GETVPN Key server

Hi,
Can I use different platforms for Key server and COOP key server ? I belive it is just IPSec or GDOI relation between the two and platform is not related. Can I have some guidelines or link from Cisco on this ? Please help
regards
Prasad

Hardware and software requirements:
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6635/ps7180/product_data_sheet0900aecd80582067.html
For more information you can visit the below listed link
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6635/ps7180/deployment_guide_c07_554713.html
Regards,
Jatin

Hardware for Java build server

I don't know if this is the correct area for the question, so I apologise if it is not...
The company I work for is budgeting a seperate build server for our developers to use. We are currently 100% sparc in the server environment. Does anyone have any real work benchmarks or experience with using different architectures for compiling code? We are looking at benchmarks between T2000, V40z, and x4200. It looks like we will get all three to get our hands on to test ourselves, but wanted to know if this has already been done and documented somewhere. The server will not be doing any application/db/etc work, just compiling. Are the FP shortcomings of the T2000 any issue with java compiliation? Would a 2x or 4x dual-core opteron be faster? Thanks in advance.

Depending on the size of your projects, the frequency of buildcycles, etc., you might just pull one of your oldest servers out of your serverfarm (and put a new one in instead) and use that.
That's the way most companies (and individuals) do it.
That machine doesn't have to be blazing fast, it hardly matters if a build takes 10 seconds or 30 for example, as usually people won't be waiting for it (or if they are they have other things to do while waiting like smoking a fag or drinking coffee which they'd otherwise do after the build was complete).
At home I use an old laptop with a Celeron 400 and 196MB RAM as my buildbox.
For my single project it's plenty fast enough, taking maybe 2 minutes when on my P4-2.4 with 1.5GB RAM it takes just over 1 minute to build the same project.
It could easily handle a lot more too, but at the moment I have no need for that excess capacity.

Mail, iCal Server and iChat server will not work over VPN

I have an Airport Extreme Base Station at the office running the network. Behind it sits a Mac Mini Snow Leopard server running 10.6.3. The ports necessary for Mail, iCal Server and iChat work fine through that external connection. I can also connect with VPN from my 10.6.3 clients.
HOWEVER, when I connect with the VPN clients, I am suddenly unable to access the Mail, iCal Server, Wiki server and iChat server. All connections time out. I can ping the server and I can do other things that do NOT work on the public Airport like ssh or VNC. ssh and VNC are closed at the airport extreme.
So it's pretty odd. When I'm connected via the VPN, all ports that are forwarded to the Snow Leopard server time out over the VPN.
I've tried various and sundry configurations with the VPN client. This includes trying to send all traffic over the VPN, moving it up in the service order, etc. etc. Nothing fixes it. DNS resolution is working fine, however when I do a wireshark capture of ppp0 traffic, I notice that SSL and TLSv1 handshakes appear to occur on the public IP address instead of the private network IP address... and they're all resets.
Has anyone gotten this to work successfully? Like I said, all ports that are NOT forwarded through the Airport work fine over the VPN, but will not work when connected to the VPN. It's really bizarre.

New data: any ports that are normally forwarded on the Airport Extreme to the Mac Mini server will not work when connected to the VPN.
For instance, if I have imaps/993 forwarded from the Airport Extreme to the Mac Mini, it works fine over the Internet. If I connect to the VPN, I can connect to all OTHER services on the Mac Mini, but Mail, for instance, will not work.

ICal Server email invitations - how to test and get this feature working

iCal Server email invitations - how to test and get this feature working
Thanks Apple for introducing this nice little feature into iCal but then completely neglecting to write any sort of useful manual that can explain what to do when it doesn't work after you set it up for the first time.
At long, long last we have finally got there after about 6 months of fiddling on and off, so I thought I had better post up the process since many have similar issues and it is hard to ascertain what is going on.
Using an external email server was just a waste of time and it still wouldn't handle the replies properly even though it was supposed to handle '+addressing'. In the end I set up a special gmail account for the iCal server and finally got it working. I list here the process of configuring and testing the system to check that each little stage is working.
Set up a Gmail account in Apple Mail to access and test in the usual way for any email account (e.g. [email protected].);
Set the iCal server email to access the same email using the following settings:
IMAP
SMTP
[email protected]
smtp.gmail.com
Port: 993 [x] Use SSL
Port: 587 [x] Use SSL
User & Pwd
Login
User & Pwd
To test the settings:
send out a test email from Apple Mail to a non-server email address that you can access to check it has been received;
send out a test email from your non-server email account to [email protected] and check that it is received;
this tells you that the GMail account is setup correctly and working
Testing iCal:
I noted that iCal was deleting any emails that arrive in the inBox in Apple Mail as soon as they arrived (this is to be expected);
test that the invites are being sent from iCal by setting an event in iCal and inviting your non-server address (you may not see any sign of this in Apple Mail but you should catch it in the iCal server log and possibly in the Gmail sent mail box);
check that the invite is received at your non-server account and Accept it in iCal on another machine - the reply is automatically sent back;
the replies appear in Apple Mail but are quickly deleted by iCal. But their record for you to see is left in Gmail under 'All Mail';
Accepted invites appear as a notification button on the top left hand bar on iCal where you click to acknowledge them and then the attendee is shown as a green circled tick instead of a grey circled ?.
this shows that iCal invitations are working correctly. Whenever an event is updated, all invitees should be updated by email automatically.
I hope this helps anyone - I could certainly have done with something similar when I started with looking at this.
Anatole
The Error and Access logfile in the Server app under iCal server are very useful in determining any errors. I got lots of imip errors when I didn't quite have the settings right. The port is critical and it won't tell you this is the problem if it fails.

iCal Server email invitations - how to test and get this feature working
Thanks Apple for introducing this nice little feature into iCal but then completely neglecting to write any sort of useful manual that can explain what to do when it doesn't work after you set it up for the first time.
At long, long last we have finally got there after about 6 months of fiddling on and off, so I thought I had better post up the process since many have similar issues and it is hard to ascertain what is going on.
Using an external email server was just a waste of time and it still wouldn't handle the replies properly even though it was supposed to handle '+addressing'. In the end I set up a special gmail account for the iCal server and finally got it working. I list here the process of configuring and testing the system to check that each little stage is working.
Set up a Gmail account in Apple Mail to access and test in the usual way for any email account (e.g. [email protected].);
Set the iCal server email to access the same email using the following settings:
IMAP
SMTP
[email protected]
smtp.gmail.com
Port: 993 [x] Use SSL
Port: 587 [x] Use SSL
User & Pwd
Login
User & Pwd
To test the settings:
send out a test email from Apple Mail to a non-server email address that you can access to check it has been received;
send out a test email from your non-server email account to [email protected] and check that it is received;
this tells you that the GMail account is setup correctly and working
Testing iCal:
I noted that iCal was deleting any emails that arrive in the inBox in Apple Mail as soon as they arrived (this is to be expected);
test that the invites are being sent from iCal by setting an event in iCal and inviting your non-server address (you may not see any sign of this in Apple Mail but you should catch it in the iCal server log and possibly in the Gmail sent mail box);
check that the invite is received at your non-server account and Accept it in iCal on another machine - the reply is automatically sent back;
the replies appear in Apple Mail but are quickly deleted by iCal. But their record for you to see is left in Gmail under 'All Mail';
Accepted invites appear as a notification button on the top left hand bar on iCal where you click to acknowledge them and then the attendee is shown as a green circled tick instead of a grey circled ?.
this shows that iCal invitations are working correctly. Whenever an event is updated, all invitees should be updated by email automatically.
I hope this helps anyone - I could certainly have done with something similar when I started with looking at this.
Anatole
The Error and Access logfile in the Server app under iCal server are very useful in determining any errors. I got lots of imip errors when I didn't quite have the settings right. The port is critical and it won't tell you this is the problem if it fails.

How to make iCal Server work both behind a firewall and externally

I've got iCal server running with a DNS record pointing to the external IP of our server and the appropriate ports open in the firewall. This is working fine. However, I can't seem to figure out how to get it recognized on the internal LAN. I tried activating DNS on the server using example.com and the actual domain name that is being used externally, but neither seemed to help get the iCal server to be recognized internally. I know there is some (probably simple) step I am missing somewhere, but I have not been able to figure it out. I've been reading the server docs and haven't been able to pinpoint what I am missing so I'm hoping someone here might be able to explain to me what the necessary steps might be.
Please try to explain this as if you're speaking to someone who is really dumb, because that's how I feel right now.
Thanks!

So you have an external static public IP, a firewall NAT, and an internal static private IP, right?
This sounds like an IP routing issue, or a DNS issue, depending on how you want to deal with it.
Either tweak your local DNS to point to your local private IP for the iCal server directly and not to the external IP address, or configure your local IP network default gateway and IP routing to allow IP to route the external IP address request out and back in through the NAT again (which is where you're probably running off the rails here), or see if iCal will allow you go go after an internal network host name in your internal DNS with your internal private IP address, or (as a test) directly after the local iCal server by its private IP address.
A whole lot of Mac OS X Server really only works "right" if you have IP and DNS configured appropriately. (I was going to write "correctly" there, but there's usually no one "correct" configuration when dealing with IP networking.)

Can connect iCal v2 (Tiger version) to iCal Server

I want to replace our office Meeting Maker server and get everyone using iCal.
However, I seem to have hit a brick wall in that I don't think non-leopard clients can use the server.
Anyone confirm that this is the case.
The documentation for using iCal server is near-useless.
Thanks
David

Hi,
Based on your description, please refer to following operations and troubleshoot this issue. Then check if
can help us to narrow down the cause of this issue.
Please type
http://server-IP-address/connect in IE. Then check if encounter the same issue.
On the Windows Server 2012 R2 Essentials, please open Internet Information Services (IIS) Manager. Navigate to Sites, then right click Default Web Site and select
Edit Bindings… In Site Bindings, select Port 80 and click “Edit…” button. Would you please provide a screenshot of the Edit Site Binding (Port 80) that you can see?
Then please click
Connect which in the list of Default Web Site. In the mid panel, select
.NET Authorization Rules and double click it. Then please check if all users were allowed.
By the way, would you please provide a screenshot of the login page when you browser
http://servername/connect? It may help me to understand this issue clearly.
Meanwhile, please logon a problematic client computer and navigate to the path: C:\ProgramData\Microsoft\Windows
Server\Logs folder. Then check if there is Computerconnector log file. If there is, please check it if can find some clues. (Please note: the log file is a hidden file. Please open Control Panel, select Folder Options, select View tab and check Show hidden
files, folders and drives. Then you will be able to find the log file.)
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Essbase 64 bit on Windows 2003 Server: recomm. Hardware for Calcparallel ?

Hi,
1 year ago, we migrated to system 9.3.1 for Hyperion Planning - as usual, this includes Workspace, Financial Reporting, Financial Analysis, SmartView, Shared Services...
everything is running well on acceptable speed and in general 2-3 times faster than our old environment- essbase 7, planning 4 on (HP DL580 G3 windows 2003 32 bit servers, with each 4 Xeon monocores @3 Ghz)
we decided 1 year ago for 3 windows servers, each with 2 Xeon quattro-cores (=8 cores @ 3.0 Ghz)
1st server Financial Reporting + Workspace (Windows Server 2003 SP2, HP Proliant BL460C G1 with 2x Quattrocore Xeon E5450 3.0 Ghz) 8 GB RAM
2nd Server Planning+Shared Services (Windows Server 2003 SP2, HP Proliant BL460C G1 with 2x Quattrocore Xeon E5450 3.0 Ghz) 4 GB RAM (8 GB would have been better)
3rd Server 64 Bit Windows 2003 with Essbase (Windows Server 64 bit SP2, HP Proliant DL380 G5 with 2x Quattrocore Xeon X5450 3.0 Ghz) 16 GB RAM
as our planning application is quiet big and we run a lot consolidation & datacopy at night, we depend on parallel calculation.
We mainly use command calcparallel 4 - but on 64 bit system, calcparallel 7 should be possible as well
We plan now to extend the system for other regions/2nd application
My Question: the new consultant confused me today, that essbase would regard 1 physicial quattrocore processor as 1 core for parallel calculation - that a machine with just 2 physical cores is not a really powerful machine... and that we better think about new hardware- that a quattrocore is just 1 core for essbase analytics - is this true ???
so did we actually choose a weak environment with only 2 (Quattro)-cores) for Essbase ?
Can anybody confirm if there is a difference for essbase between having e.g. 4 Dualcores and 2 Quattrocores ? (Besides the fact, that it will cost more, as we have to lease a bigger Server with more processor-sockets- and that it will cost a lot efforts to get the system changed)
P.S.: EAS console shows 8 cores for the Essbase Server in properties
Applicationlogfile shows: calculating in parallel with [4] threads (we use command calcparallel 4 in businessrule)
- our nightly calculations take between 60 and 120 minutes- if we avoid fragmentation (run dense restructure every 4 weeks) and keep the system clean and lean...

Hi John,
thanks for the helpful link - the long discussion reminded me again, that pure cores and cache is not all, what makes up a good essbase application -
I will test with calcparallel 6 (in comparison to 4) on our 64bit environment - just to see if I can achieve a 10, 20 or 30% improvement...
In addition, I must admit, that 50% of our 1-2 hour calculation is calculated in serial/ not parallel... so I expect an additional 5 to 10 min improvement, not more.
Thank you for now

Asking again: any fixes for http:/1.1 300 and 500 errors in iCal-Server?

Hi there
I've set up several OS X servers in the last few months, most of them with ical services up and running. Quite everything works smooth, but most customers experience sooner or later errors like
http:/1.1 300... (mostly with repeating events, which seem to be buggy in iCal&CalDAV already for a long time)
http:/1.1 500...
neither are there any relevant entries in the log, nor does it occur on a regular base - in fact, we can observe these errors all 2 or 3 weeks or so. Stopping an restarting of iCal services usually fixes them. DNS is set up perfectly well, including the SRV-entries.
What about you? Do we just have to live with these errors? Or do I really have to sell Kerio to my customers?
Thanks for any suggestion
Regards
Roman

Hi Roman
I have had a few years setting up and administering various calendar options on Xserve.
The Apple built in iCal server is by far the worst of the lot.
Previous to that we used phpicalendar- http://phpicalendar.net/documentation/index.php/Main_Page
It is a bit dated and does not support the same feature set as the Apple one. It works well though.
Kerio on the other hand is great, works well and is easy to use, apart from accepting invites on iOS devices. Its also a much better mailserver than Apple's one.
Another option is to write a script to run everyday to stop and restart the ical service?

ICal Server external Email Invitations Not working for names with umlauts!!

Hi,
I was testing external email invitations with iCal Server on Lion Server and encountered that if a Name that can Be resolved via iPhone or mac addressbook or even the sending iCal Account contains an umlaut something like this show up in iCal Server error log:
2011-09-26 17:01:18+0200 [-] [mailgateway] 2011-09-26 17:01:18+0200 [-] [twext.web2.server#error] [Failure instance: Traceback: <type 'exceptions.UnicodeDecodeError'>: 'ascii' codec can't decode byte 0xc3 in position 90: ordinal not in range(128)
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/internet/defer.py:388:errback
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/internet/defer.py:455:_startRunCallbacks
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/internet/defer.py:542:_runCallbacks
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/internet/defer.py:1076:gotResult
2011-09-26 17:01:18+0200 [-] [mailgateway]      --- <exception caught here> ---
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/internet/defer.py:1018:_inlineCallbacks
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/python/failure.py:350:throwExceptionIntoGenerator
2011-09-26 17:01:18+0200 [-] [mailgateway]      /usr/share/caldavd/lib/python/twistedcaldav/resource.py:310:renderHTTP
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/internet/defer.py:1018:_inlineCallbacks
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/python/failure.py:350:throwExceptionIntoGenerator
2011-09-26 17:01:18+0200 [-] [mailgateway]      /usr/share/caldavd/lib/python/twext/web2/static.py:127:renderHTTP
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/internet/defer.py:1018:_inlineCallbacks
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/python/failure.py:350:throwExceptionIntoGenerator
2011-09-26 17:01:18+0200 [-] [mailgateway]      /usr/share/caldavd/lib/python/twext/web2/resource.py:109:renderHTTP
2011-09-26 17:01:18+0200 [-] [mailgateway]      /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /twisted/internet/defer.py:1020:_inlineCallbacks
2011-09-26 17:01:18+0200 [-] [mailgateway]      /usr/share/caldavd/lib/python/twistedcaldav/mail.py:334:http_POST
2011-09-26 17:01:18+0200 [-] [mailgateway]      /usr/share/caldavd/lib/python/twistedcaldav/mail.py:958:outbound
2011-09-26 17:01:18+0200 [-] [mailgateway]      /usr/share/caldavd/lib/python/twistedcaldav/mail.py:1199:generateEmail
2011-09-26 17:01:18+0200 [-] [mailgateway]      ]
2011-09-26 17:01:18+0200 [-] [caldav-1] [AuthorizedHTTPGetter,client] [twistedcaldav.scheduling.imip#error] Could not do server-to-imip request : <twistedcaldav.scheduling.imip.ScheduleViaIMip object at 0x103c65ed0> 500 Internal Server Error
2011-09-26 17:01:18+0200 [-] [caldav-1] [AuthorizedHTTPGetter,client] [twistedcaldav.scheduling.scheduler.ScheduleResponseQueue#error] Error during PUT for mailto:someemailaddress@yourdomain: iMIP request failed
And No Email is send!
If changing the Umlaut ü to something like ue in the Sender or Receiver Name everything is alright!
Thank you Apple for obviously Not testing Lion Server for international use :-/
Maybe this help someone else who is using umlauts with iCal Server external Email invitations
Regards
Eldrik

Hello Daryn,
Thinks for commenting. I am very upset that Apple just said "No" when I asked for this to be fixed. There appears to be no way to submit this as an official bug that keeps ical from running.
Apple actually had me reinstall my whole server and the issue was still there and then they just said "Oh, well I will email someone about it.".
This is the first time Apple has stunk it up in my books. This is bad support for Server.
Brad

Hardware Sizing for Oracle Application Server and MapViewer

Hi all,
I need to develop an application using Oracle Application Server 10g and MapViewer. The applicaction will, basically, do thematic maps based on a search criteria. The estimative is that we will have 25 users simultaneously using it.
I´d like to have an idea about the hardware to support it.
Do you know where I can get this information?
Any documentation can help.
Regards,
Luis Augusto

Hi Luis,
It may depend on your database size, but I think at least you need to meet the minimum requirements for the Application Server. You can find additional documentation for the AS at http://www.oracle.com/technology/products/ias/index.html.
However I would suggest some extra memory, and if possible the better CPU that you can get. MapViewer will render the spatial features on the server side, and depending on your database size and number of features returned from the queries, this extra memory will help.
Joao

Swap hardware for 10.2 database Linux (datafiles reside on SAN server).

Hello Gurus,
I am planning to upgrade hardware for two production database servers (currently Oracle 10.1.0.3.0 on Linux AS3 32bit) to New Dell Poweredge 6850 64 bit Linux AS4 upgrqade 7, Oracle 10.2.0.4.0 with replication enabled on certain tables.
The database tablespaces and datafiles exist on a SAN storage server. I was wondering what is the fastest way to hook up the new servers and migrate or integrate the currrent two databases into the new hardware. I was looking at the old "export/import" but that would have some serious downtime. Transportable Tablespaces looks like an option- but I have no experience in it.
My new servers have Oracle 10.2.0.4.0 installed and the servers are named the same as the old servers. Is there a way to have the new servers point to the SAN storage and just "pick up" the existing tablespaces and datafiles for the existing two databases? I have retained the block_size on the new configuration of 8K.
What is the fastest way to get the new hardware up and running connecting to a SAN storage device "seeing" the old database.
I would love any advice, I have a metalink account- but I thought this type of question would be better suited for the masses of experts out there who may have gine through this exercise before.
Cheers,
blakey

Seems You want to migrate from 32bit architecture to 64bit?
Then for upgrade to 10gR2 see metalink note 316889.1
And as oracle will change from 32bit to 64bit as well (not only linux will 64 bit, but oracle software as well), then additional step for changing wordsize to 64bit is needed. And that is described in metalink note 62290.1
Migration: as Your db is on san storage (everything including controlfiles, parameter files and so on) - then create equal mountpoints on new server (stop databases on old server, mount db related disks from storage to the new server) and that's it - next part is upgrade and migration to 64bit wordsize.
Probably oracle software is installed on local disks and that means You will have to manualy copy $ORACLE_HOME/dbs - spfile, password file to the new server. And of course listener.ora, tnsnames.ora files as well.
You can reffer to this metalink note 363609.1 for more details
Of course, before go through all configuration (/etc/sysctl.conf and so, create equal /etc/oratab and adjust oracle user profile for new server).
And before starting anything - take a full backup of oracle database (hot or cold, whatever You preffer).

Minumum hardware requirement for Siebel Document server?

what is the minimum hardware requirement for Siebel document server?

To install the Document Server, perform the following steps:
Obtain the required hardware.
Install the Siebel Server.
Install third-party applications.
After installing the Siebel Server, you may have to follow some of the steps described in Configuring the Document Server. The Document Server is a component of Siebel eDocuments, which can be installed during installation of the Siebel Server. Consult with your system administrator to verify that the Document Server has been installed and configured according to the requirements listed in the following sections.
Hardware Requirements
The Document Server is supported on the Windows 2000 platform. To maintain stability and performance, the Document Server must run on a dedicated host machine. The Siebel Server on this machine should host one instance of the Siebel eDocuments component group. No other components should be running other than required system components.
To support more users, you can run additional instances of the Siebel eDocuments component group on additional dedicated host machines.
Installing the Siebel Server
Install the Siebel Server on the dedicated host machine of the Document Server. For more information about installing the Siebel Server, see Siebel Server Installation Guide for Microsoft Windows.
During installation, you will have the option to enable component groups. Select the Siebel eDocuments component group. Do not enable any other component groups.
This step can also be performed after installation is complete, as described in the section Enabling the Component Group.
Installing Third-Party Applications
You must install Microsoft Word.
To install Microsoft Office
Log on to the server machine using the same user account that the Siebel Server NT service uses. This user account must belong to the Administrators group.
NOTE: The install must use the same account to be used by the NT Service. The installer configures COM security settings so that the installing user account will have the correct permissions to access and launch the application. If the install uses an account other than the Siebel Server NT service account, errors may occur when the Document Server tries to launch the application.
Install Microsoft Office using a Typical, or complete, installation. Verify that your version of Microsoft Office will install the Web Authoring Tools (HTML) component with the Typical installation. If it does not, you will need to use the Custom installation option, and install all of the typical components as well as the Web Authoring Tools (HTML) component.
Start the applications that will be used by the Document Server. This forces the applications to register themselves.
Close the applications.
Regards,
Joseph Arul Dass

Hardware Requirements for a Windows Server 2012 Domain Controller.

Hi,
I have a secondary office with 10 users with a domain controller that has reached its end of life. We like to upgrade the current hardware to serve as a domain controller and potentially as an onsite file server that will sync with head office during
off peak business hours.
Any recommendations for a low cost yet reliable hardware for the above solution ?

Hi,
Thanks for your post.
I think you need to meet the requirement for upgrading to windows server 2012r2.
http://technet.microsoft.com/en-us/library/hh994618.aspx#BKMK_SysReqs
And you could refer to the following article about windows server 2012r2 domain controller configuration
Building Your First Domain Controller on 2012 R2
http://social.technet.microsoft.com/wiki/contents/articles/22622.building-your-first-domain-controller-on-2012-r2.aspx
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

ICal Server Keeps Prompting Users for password

Hello All!
I am having issues with a MacMini Server iCal Server prompting users for their password. They are getting the following message:
iCal can't log in to your account becuase your password may be incorrect. The user clicks cancel and they can contenue working however they a few min later they will get prompted again. The user can enter thier password, click ok and a few min later they get prompted again. This goes on all day!
Any ideas on how to resolve?
MacMini Lion Server 10.7.3
Thanks,
ebrind

Thanks Jonathan! Here it is:
Oct 24 2012 15:49:12 AUTH2: {0x4f9af0524882219c0000000800000008, XXXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:12 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:12 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:13 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:14 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:15 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:15 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:15 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:15 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:15 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:17 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:17 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:17 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:49:19 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:53:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 15:53:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:03:30 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:03:31 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:03:34 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:03:37 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:03:40 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:04:14 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:04:46 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:04:46 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:04:48 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:04:48 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:04:49 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:05:11 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:05:13 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:05:13 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:05:14 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:05:29 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:10:17 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:10:20    AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:10:22 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:13:49 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:13:51 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:13:54 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:14:39 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:14:40 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:14:40 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:14:58 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:19:12 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:19:13 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:19:15 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:19:17 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:19:18 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:23:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:23:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:24:18 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:24:20 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:24:22 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:26:17 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:26:17 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:27:48 KERBEROS-LOGIN-CHECK: user {0x4f9af0524882219c0000000800000008, XXX} is in good standing.
Oct 24 2012 16:27:48 KERBEROS-LOGIN-CHECK: user {0x4f9af0524882219c0000000800000008, XXX} authentication succeeded.
Oct 24 2012 16:27:48 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} DIGEST-MD5 authentication succeeded.
Oct 24 2012 16:28:03 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:28:03 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:28:04 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:28:04 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:28:05 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:28:18 KERBEROS-LOGIN-CHECK: no principal ([email protected])
Oct 24 2012 16:28:50 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} DIGEST-MD5 authentication succeeded.
Oct 24 2012 16:29:03 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:29:03 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:12 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:34 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:34 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:36 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:36 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:37 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:37 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:37 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:37 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:43 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:34:43 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:41:00 AUTH2: {0x4f9aef1b6b8b45670000000400000004, servername.local$} DHX authentication succeeded.
Oct 24 2012 16:41:38 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} is in good standing.
Oct 24 2012 16:41:38 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} authentication succeeded.
Oct 24 2012 16:42:32 AUTH2: {0x4f9aef1b6b8b45670000000400000004, servername.local$} DHX authentication succeeded.
Oct 24 2012 16:43:11 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} is in good standing.
Oct 24 2012 16:43:11 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} authentication succeeded.
Oct 24 2012 16:43:41 AUTH2: {0x4f9aef1b6b8b45670000000400000004, servername.local$} DHX authentication succeeded.
Oct 24 2012 16:43:48    AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:43:48 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:44:19 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} is in good standing.
Oct 24 2012 16:44:19 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} authentication succeeded.
Oct 24 2012 16:46:49    KERBEROS-LOGIN-CHECK: user {0x4f9af0524882219c0000000800000008, XXX} is in good standing.
Oct 24 2012 16:46:49 KERBEROS-LOGIN-CHECK: user {0x4f9af0524882219c0000000800000008, XXX} authentication succeeded.
Oct 24 2012 16:46:49 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} DIGEST-MD5 authentication succeeded.
Oct 24 2012 16:50:18 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:50:18 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:50:18 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:50:19 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:50:58 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:50:58 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:00 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:00 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:00 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:00 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:01 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:01 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:05 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:05 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:06    AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:11 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:11 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:57 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:51:57 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:53:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 16:53:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:01:38 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:01:38 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:07:05 KERBEROS-LOGIN-CHECK: no principal ([email protected])
Oct 24 2012 17:07:36 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} DIGEST-MD5 authentication succeeded.
Oct 24 2012 17:11:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:11:25 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:21:18 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:21:18 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:23:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:23:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:24:06    AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:24:07 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:24:08 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:24:12 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:30:27 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:30:27 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:30:32 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:31:03 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:31:03 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:35:17 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} is in good standing.
Oct 24 2012 17:35:17 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} authentication succeeded.
Oct 24 2012 17:35:50 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:35:50 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:40:48 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:40:48 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:41:02 AUTH2: {0x4f9aef1b6b8b45670000000400000004, servername.local$} DHX authentication succeeded.
Oct 24 2012 17:41:40 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} is in good standing.
Oct 24 2012 17:41:40 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} authentication succeeded.
Oct 24 2012 17:42:35 AUTH2: {0x4f9aef1b6b8b45670000000400000004, servername.local$} DHX authentication succeeded.
Oct 24 2012 17:43:13 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} is in good standing.
Oct 24 2012 17:43:13 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} authentication succeeded.
Oct 24 2012 17:43:43 AUTH2: {0x4f9aef1b6b8b45670000000400000004, servername.local$} DHX authentication succeeded.
Oct 24 2012 17:44:21 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} is in good standing.
Oct 24 2012 17:44:21 KERBEROS-LOGIN-CHECK: user {0x4f9aef1b6b8b45670000000400000004, servername.local$} authentication succeeded.
Oct 24 2012 17:46:48 KERBEROS-LOGIN-CHECK: user {0x4f9af0524882219c0000000800000008, XXX} is in good standing.
Oct 24 2012 17:46:48 KERBEROS-LOGIN-CHECK: user {0x4f9af0524882219c0000000800000008, XXX} authentication succeeded.
Oct 24 2012 17:46:48 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} DIGEST-MD5 authentication succeeded.
Oct 24 2012 17:50:59    AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:50:59 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:51:01 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:51:01 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:51:02 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:51:02 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:51:02 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:51:02 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:51:07 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:51:07 AUTH2: {0x4f9af032312303780000000700000007, QQQ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:52:56 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:52:59 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:52:59 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:52:59 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:52:59 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:52:59 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:52:59 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:00 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:00 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:00 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:01 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:01 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:01 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:01 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:01 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:02 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:02 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:02 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:03 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:04 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:05 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:05 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:07 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:08 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:10 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:10 AUTH2: {0x4f9af0786fe3211a0000000900000009, YYY} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:11 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:11 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:13 AUTH2: {0x4f9af0524882219c0000000800000008, XXX} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:53:25 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:55:33 AUTH2: {0x4f9aeff441377b7c0000000600000006, ZZZ} WEBDAV-DIGEST authentication succeeded.
Oct 24 2012 17:55:33 AUTH2: {0x4f9bbf3c45a1f0200000000a0000000a, WWW} WEBDAV-DIGEST authentication succeeded.
XXXX means user A
YYYY means user B etc, etc

Hardware for an iCal Server?

Similar Messages

Maybe you are looking for