Msft Passion

OCS 2007 R2 : A/V Edge Auhentication server errors

2009-05-22T07:27:00.000-07:00

Il client LIVE MEETING non avvia il flusso AUDIO/VIDEO e "magari" riscontrate degli errori di autenticazione da parte dell' A/V Edge server?
HEHEHEHEHE........... http://www.pro-exchange.eu/modules.php?$1&name=News&file=article&sid=1122 !!!! INCREDIBILE MA VERO!!! NO COMMENT!!!!

"FORMAT C: /U"

Windows 2003 : The File Replication Service has detected that the replica set "1" is in JRNL_WRAP_ERROR

2009-04-23T00:26:00.000-07:00

Ovviamente poteva mancare questo problema....... no no!Proprio no!Non ci facciamo mancare niente!
Magari salta la corrente in una sede remota e l'ups, pagato fior di quattrini, decide di non fare il suo lavoro ovvero tenere in vita il povero DC: appunto!
E dai che sarà mai.... IM GOOGLING!

Cosi come riportato da MSFT :
Troubleshooting FRS Event 13568
FRS event ID 13568 contains the following message:The File Replication Service has detected that the replica set "1" is in JRNL_WRAP_ERROR.
NTFS maintains a special log called the NTFS USN journal, which is a high-level description of all the changes to files and directories on an NTFS volume. FRS uses this mechanism in order to track changes to NTFS directories of interest, and to queue those changes for replication to other computers. The NTFS USN journal has defined size limits and will discard old log information on a first-in, first-out basis in order to maintain its correct size.
If FRS processing falls behind the NTFS USN journal, and if NTFS USN journal information that FRS needed has been discarded, then FRS enters a journal wrap condition. FRS then needs to rebuild its current replication state with respect to NTFS and other replication partners.
Each file change on the NTFS volume occupies approximately 100 bytes in this journal (possibly more, depending on the file name size). In general, the NTFS USN journal for an NTFS volume should be sized at 128 megabytes (MB) per 100,000 files being managed by FRS on that NTFS volume.
In Windows 2000 SP2 and earlier, the default journal size is 32 MB and the maximum journal size is 128 MB. In Windows 2000 SP3, the default journal size is 128 MB, and the maximum journal size is 10,000 MB
The journal size can be configured with a registry subkey, but keep in mind that once you increase journal size you should not lower it again because this will cause a journal wrap. To learn how the USN journal size can be increased see Knowledge Base article 221111: Description of FRS Entries in the Registry. To view this Knowledge Base article, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources/.
FRS can encounter journal wrap conditions in the following cases:
Many files are added at once to a replica tree while FRS is busy, starting up, or not running.
On a server that is being used for authoritative restore, or as the primary server for a new replica partner, excessive file activity at the start of this process can consume NTFS USN journal records. Size the NTFS volume at 128 MB per 100,000 files being managed by FRS, as mentioned above, to avoid this condition.
NTFS needs to be processed with Chkdsk and Chkdsk corrects the NTFS structure. In this case, NTFS creates a new NTFS USN journal for the volume or deletes the corrupt entries from the end of the journal.
The NTFS USN journal is deleted or reduced in size.
FRS is in an error state that prevents it from processing changes in the NTFS USN journal.
If FRS is experiencing journal wrap errors on a particular server, it cannot replicate files until the condition has been cleared. To continue replication, the administrator must stop FRS on that server and perform a non-authoritative restore of the data so that the system can synchronize with its replication partners. For more information about performing a non-authoritative restore, see "Performing a Non-Authoritative Restore" in this guide.
Note the following:
Windows 2000 SP1 cannot perform this process automatically.
In Windows 2000 SP2, FRS performs this process automatically.
In Windows 2000 SP3, FRS does not perform this process automatically. The reason for this change was that it was typically being performed at times that were not planned by administrators. However, a registry setting is available that allows FRS to perform the automatic nonauthoritative restore, just as in Windows 2000 SP2. However, it is recommended to leave this as a manual process.
For more information about performing the nonauthoritative restore process on a server, see Knowledge Base article 292438: Troubleshooting Journal Wrap Errors on SYSVOL and DFS Replica Sets. To view this Knowledge Base article, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources/.

Reg2Adm : converte chiavi di reg in file .adm

2009-04-23T00:20:00.000-07:00

Molto utile....

http://www.novell.com/coolsolutions/tools/13885.html

Ciauz.

Windows 2003 : le cartelle NETLOGON e SYSVOL sono "magicamente" sparite ....

2009-04-22T23:54:00.000-07:00

... e magari dopo aver eseguito delle verifiche funziali con il tool DCDIAG, ottenete il seguente messaggio di errore :
"DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355".
Il set di replica della cartella SYSVOL non riesce ad individuare un partner valido....magari un DC rimosso "AD MINCHIAM" ovvero secondo procedure non "supportate" da MSFT.
Per ovviare al problema occorre modificare delle chiavi di reg, come indicato nella seguente KB MSFT :

http://support.microsoft.com/kb/316790/en-us

..... Next,Next,Next .... OPPS!

Hyper-V : RPC error

2009-02-02T02:37:00.000-08:00

Nel gestire da remoto un Hyper-V server si potrebbe incontrare un meraviglioso errore "RPC" che può essere risolto seguendo la procedura descritta nel seguente blog :

http://blogs.technet.com/jhoward/archive/2008/11/14/configure-hyper-v-remote-management-in-seconds.aspx

Utilizzando lo script "hvremote" sia lato server che client è possibile, in pochi minuti, gestire da remoto un Hyper-V server senza problemi.

MCITP: Enterprise Administrator certification

2009-01-15T08:20:00.000-08:00

Sono disponibili i nuovi esami di certificazione in ambiente Windows 2008....never ending story :

http://www.microsoft.com/learning/mcp/mcitp/windowsserver/2008/enterprise/default.mspx

per fortuna l'upgrade path per chi possiede la certificazione MCSE su Windows 2003 non è cosi drammatico: il delta è "solamente" di 3 esami.

Exchange 2007 ( transition from exchange 2000/2003 )

2009-01-15T04:13:00.000-08:00

Step-by-step su come eseguire un passaggio ( transition) dalla piattaforma di messaggistica Exchange 2000 - 2003 al "nuovo" sistema di posta MSFT, ovvero Exchange 2007.

http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part1.html

Deploy ActiveX con privilegi utente.

2009-01-15T03:21:00.000-08:00

I problemi che si riscontrano sono legati al "cosa" viene eseguito nelle macchine a seguito dell'esecuzione di ActiveX, e sembra che non ci siano metodi "indolore" per by-passare tale issue.

Riporto di seguito dei link che trattano la tematica:

http://support.microsoft.com/default.aspx?scid=kb;en-us;280579

http://technet.microsoft.com/en-us/magazine/2007.07.axis.aspx

http://technet.microsoft.com/en-us/magazine/2006.11.uac.aspx

http://technet.microsoft.com/en-us/library/cc721964.aspx

HTH