You can install ST 8.5 using Domino 8.5.0, but if you want Domino 8.5.x see these links:
http://www-10.lotus.com/ldd/stwiki.nsf/dx/Sametime_8.5_issues_on_Domino_8.5.1
http://www-01.ibm.com/support/docview.wss?uid=swg21418535
You can install ST 8.5 using Domino 8.5.0, but if you want Domino 8.5.x see these links:
http://www-10.lotus.com/ldd/stwiki.nsf/dx/Sametime_8.5_issues_on_Domino_8.5.1
http://www-01.ibm.com/support/docview.wss?uid=swg21418535
Vejam a reportagem neste link e usem a ferramenta neste link –> http://www.ceptro.br/Simet
Faça o teste identificado e também ajude a divulgar o SIMET: além de ajudá-lo a verificar se a sua conexão Internet está OK, ele ajuda o NIC.br e o CGI.br a obterem informações sobre as conexões Internet em todo o Brasil. Isso permitirá que outras ações sejam tomadas, em favor da melhoria da qualidade da infraestrutura Internet no paÃs.
Vejam o meu resultado, não vou colocar o provedor para não fazer propaganda :-), nada mal
It is a common situation and when the account is removed from Domino Directory bad things cam appear, like this message:
[27718:00265-4009925536] 05/05/2010 11:39:10 AM Policies and settings documents signed by XYZ/Acme are no longer valid because this person does not have the required access level or roles to the Domino Directory.
It is about Policies and you solve the problem with this:
In the Policies (or Settings) view, check all policies you want to resign then choosed ‘Actions -> Resign Policy’
IBM published this TN about the issue.
Scenarios known to lead to the issue
(1) You have a busy application with many users updating, adding and/or deleting documents in it. While that is happening, an agent is running and using the same view(s) to retrieve data. The agent will start to do its job and then get a message that the view is no longer current. It will back out, ask for a view refresh, and then try again. Since the application is very busy with many people, as soon as the agent moves forward again, the view is again no longer current. This loop will repeat at most 10 times, after which the error “The collection has become invalid” will be returned.
(2) You have an application accessed via HTTP, where many HTTP users are executing an agent that is calling GetDocumentByKey or GetAllDocumentsByKey, and these agents (HTTP users) are also creating, updating and/or deleting documents. If they are all in the same view, then things can back up and the loop might run 10 times and fail with the error. Replication moving data into the application at the same time could serve to make things worse.
(3) You have an application that is busy for reasons other than many users working in it. While that is happening, an agent is running and using the same view(s) to retrieve data. The agent will start to do its job and then get a message that the view is no longer current. It will back out, ask for a view refresh, and then try again. Since the application is very busy with things changing the state of the documents, as soon as the agent moves forward again, the view is again no longer current. This loop will repeat at most 10 times, after which the error “The collection has become invalid” will be returned.
We believe firmly that these scenarios actually are not common to properly resourced Domino servers.
Our commitment & plans
We are committed to delivering a high-quality, comprehensive solution.
Note: The preferred and recommended way to resolve defects in your Notes/Domino environment is to stay current with the latest maintenance releases and fix packs, both which undergo formal test cycles to ensure quality. Hotfixes are effective when you experience business critical defects that cannot wait for the next maintenance release or fix pack. However before requesting any hotfix, please take into consideration that they receive less test and deployment, and thus they inherently carry more risk.
Specifically regarding SPR CSCT836HF, if you are not running scenarios like the ones described above, then you’ll have no need for the hotfix. Additionally, if you are running those scenarios, but have no evidence of the error “The collection has become invalid”, then you’ll have no need for the hotfix.
Notes 7 is supported on Windows but I’m finding that there are some problems, when i try to use audio with the sametime integrated client.
I opened an PMR and got this answer:
The integrated sametime client does not support audio and video according to the TN 7016451
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg27016451
Very bad.
Windows 7 is a supported Operating System for iNotes starting with Domino 8.5.1 Fixpack 1 with iNotes Hotfix 304.2CHF1. Future maintenance releases and major releases will support Windows 7 and will not require an iNotes hotfix.
iNotes cumulative hotfix 304.2CHF1 is available on Fixcentral.
Joining a Windows 7 workstation to a Lotus Foundations server configured as a domain controller is not currently supported. If a Windows 7 workstation is configured in workgroup mode, it can use the file sharing services on a Lotus Foundations server.
Attempts to join a Lotus Foundations domain controller from a Windows 7 workstation will result in the following error:[
The specified domain either does not exist or could not be contacted.
]
Providing compatibility between Windows 7 workstations and Lotus Foundations based domain controllers is a high priority for IBM and a fix is on our road map.
The information above is from TN1409287
If you upgrade the Notes Client from any version to 8.5.1 and the names.nsf, does not get upgraded, Open the notes.ini and search for TemplateSetup= and then set TemplateSetup=0 restart the Notes client. The Design task will run and make the upgrade.
One of my Domino servers is running for almost 180 days without problems. We are now planning to upgrade to version 8.5.1 FP2
Meu servidor está executando por quase 180 dias sem problemas. Estamos planejando agora o upgrade para versão 8.5.1 FP2
Lotus Domino (r) Server (Release 8.0.2FP1 for UNIX) 08/04/2010 21:40:12
Server name: Pullo/PlansisNet/Plansis
Domain name: PLANSIS
Server directory: /local/notesdata
Partition: .local.notesdata
Elapsed time: 172 days 11:02:03
Transactions/minute: Last minute: 13; Last hour: 26; Peak: 1171
Peak # of sessions: 116 at 27/01/2010 13:42:49