Homeslice - Just Like a Boss

Group Policy Replication Errors - How to Fix All of a sudden one of your workstations seems to not be able to update its own group policy objects. It appears that the workstation has failed the trust relationship. For Example C:\Users\Biff> gpupdate /force Updating Policy... User Policy update has completed successfully. Computer policy could not be updated successfully. The following errors were encountered: The processing of Group Policy failed. Windows attempted to read the file \\homeslice.net\SysVol\homeslice.net\Policies\{2B44EB00-32DD-42E3-8C83-9B6C6CA6D 6D6}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller  has not replicated to the current dom...

Use the tcpdump command on linux to monitor network traffic. Here are some of my favourite recipies for tcpdump success.  My little cookbook shows typical TCPDump tasks. 0) Monitor Web Traffic 1) Monitor web service traffic on an apache server. given that your server has an eth0 network port. If your web client device is at 192.168.99.10, this following command will monitor all traffic from that device that enter eth0 on port 80. tcpdump -i eth0 -vvv tcp port 80 and src 192.168.99.10 Options:  -vvv       Verbose dump of network headers                 -i           network interface selector                 -A         Display all cleartext packet details. (optional) 1)Dump SIP Traffic from eth0 E...

Suddenly it happens, you start seeing this message in your exchange 2010 OWA When they try to open an e-mail with outlook web acces. They get the following error message Rights management operation failed . OWA error Rights management operation failed Ouch! What to do? Open exchange powershell  First step is to figure out that IRM is enabled in your exchange 2010 Next step is to figure out what your identity is: in this case the full identit is EXCHANGE2010\owa (Default Web Site) Final step is to turn off the doggone IRM!  Using the identity located in step 2.   1. Log on to the exchange server and open (as Administrator) the Exchange Management Shell (EMS) 2. Run "Get-OWAVirtualDirectory | FL" and search for IRM; you'll probably see that it's enabled. 3. Run "Set-OWAVirtualDirectory -IRMEnabled $false" or you could provide the name of the identity using the -Identity "<identity goes here>" for example: [PS] C:\Windo...