This can be fixed quite easily. Open Active Directory Users and Computers and locate the security group that represents the distribution list. Right-click the object and choose Properties, then click the Managed By tab. Check the box that says "Manager can update membership list" and the user should now be able to make changes to the DL.

LIKE NEW 70-236: Microsoft Exchange Server 2007 Configuration

US $40.00

3h 43m

Microsoft Exchange Server 2010 Best Practices (2010,...

US $29.99

8d 2h 50m

Learn Microsoft Exchange Server 2003 - IT Training Tutorial

US $19.95

19d 20h 25m

MICROSOFT T-SHIRT windows 7 exchange xp server 2008

US $8.49

16d 16h 44m

Microsoft Windows Advanced Server 2000 & 2002 Exchange SQL Host Commerce Biztalk

US $99.50

1d 18h 35m

Microsoft Exchange Server 2007 by Joshua Maher, Scott Lowe, Walter Glenn...

0 Bid

US $8.99

1d 19h 20m

NEW - Mastering Microsoft Exchange Server 2010

US $18.08

6d 2h 11m

MICROSOFT T-SHIRT windows 7 exchange xp server 2008

US $8.49

16d 16h 44m

Microsoft Exchange Server 2003 Training Tutorial CD NEW

US $11.89

17d 13h 13m

MICROSOFT T-SHIRT windows 7 exchange xp server 2008

US $8.49

16d 16h 44m

Powered by phpBay Pro

Windows 7 - Turn on Advanced Network Settings

Open Control Panel.

Click on Network and Sharing Center.

Click Change Adapter Settings.

Press and release the Alt key (see photo below), and the menu will be displayed.



Click Advanced and then Advanced Settings.

You can now change the binding order.

V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine

The job also show a 0 byte count. When you check the Backup Exec Remote Agent for Linux on the system you are trying to backup you find that the VRTSralus daemon is stopped. After starting the agent the job will run successfully for a few times, but then the job will fail again with the same error message. Again you find that the VRTSralus daemon is stopped. In order to prevent the agent from stopping you can create a watchdog script which will monitor the beremote process and automatically restart it if it is not running.

Watchdog Script Used to Monitor VRTSralus Daemon

#!/bin/bash
#
# watchdog
#
# Run as a cron job to keep an eye on what_to_monitor which should always
# be running. Restart what_to_monitor and send notification as needed.
#
# This needs to be run as root or a user that can start system services.

NAME=beremote
START="/etc/init.d/VRTSralus.init restart"
NOTIFY=name@domain.com
GREP=/bin/grep
PS=/bin/ps
NOP=/bin/true
DATE=/bin/date
MAIL=/bin/mail
RM=/bin/rm

$PS -ef|$GREP -v grep|$GREP $NAME >/dev/null 2>&1
case "$?" in
0)
# It is running in this case so we do nothing.
$NOP
;;
1)
echo "$NAME is NOT RUNNING. Starting $NAME and sending notices."
$START 2>&1 >/dev/null &
NOTICE=/tmp/beremote_watchdog.txt
echo "$NAME was not running and was started on `$DATE`" >> $NOTICE
#   $MAIL -n -s "watchdog notice" $NOTIFY < $NOTICE
#   $RM -f $NOTICE
;;
esac

exit

This script will create a log in the /tmp directory and keep track of each time that the watchdog restarts the VRTSralus daemon. You will need to setup a cron job and schedule it to run at a set interval, such as every 15 minutes to ensure the remote Linux agent gets restarted.

Overview

This behavior was experienced by a user trying to update the Business Phone attribute in the GAL to display internal phone extensions of employees. The Active Directory Telephone number attribute for each user object was updated, but the GAL was not displaying the updated Business Phone extensions. At first this was believed to be a synchronization issue with cached mode because when cached mode was disabled the GAL would display the updated phone extensions, but a gaining a better understanding of the Offline Address Book will shed some light on this behavior.

Exchange Cached Mode

When you enable Exchange Cached Mode in Outlook a copy of your mailbox and the Offline Address Book (OAB) is copied to your local computer. This mode was created to counter slow network latency issues that would slow down Outlook because it was constantly connecting to the Exchange server. With cached mode enabled Outlook will use both the offline and online copies of your mailbox to deliver a better user experience with Outlook slowing to a crawl when doing simple tasks like switch to a different folder.

How the Offline Address Book Works in Exchange

Exchange generates the OAB files every24 hours, or once per day, at 5:00 am by default. You can force Exchange to update the OAB more frequently but it is not recommended. The Outlook client will check for updates to the OAB once every 24 hours, but each Outlook client might check for updates at a different time and therefore can have different a different version of the OAB. For example, the server will update the OAB at 5:00 am, but one Outlook client might check for updates at 10:00 am, but another client might not check until 5:00 pm. During that 7 hours the 2 clients would have different versions of the OAB.

When the Outlook client checks for updates to the OAB it will first attempt to download the differential files and not the full OAB in order to prevent network congestion, but if the differential files are greater than 1/8 of the size of the full OAB then Outlook will download the entire copy of the OAB. That might happen in the event that there have been a lot of updates to the directory in the past 24-48 hours, such as when an area code is changed and every user is affected.  Outlook can be forced to download the updated OAB by clicking on Tools>then Send/Receive> then click Download Address Book. You’ll have to close Outlook and re-open and it will start before the download will start. Keep in mind that this will only download the changes that occurred prior to 5:00 am when Exchange generated the updated Offline Address Book. If changes were made after Exchange generated the OAB, then you would have to force Exchange to update the OAB and then force Outlook to download the address book, but this practice is not recommended by Microsoft.

Troubleshooting OAB problems

If you are troubleshooting an issue and want to confirm whether you are looking at the Offline Address Book or if you are pulling the online address book there is a simple way to check. Open the Address Book and right-click on Global Address List, then click Properties. It will display The current server is: and then path. If the path is pointing to a local drive then you are obviously using the offline address files. If the path points to a domain controller then you are using the online copy of the address book. You can see examples of each below:

Local OAB

Online Global Address List

Summary

That about covers the basics of the Offline Address Book and how it is downloaded to Outlook from the Exchange Server. Hopefully this has helped you if you were unclear at all on how the OAB works in Exchange. If you have questions please leave them below and I will answer them or if you have a comment I also appreciate hearing those as well. Thanks for stopping by.

MCITP Design & Deploy Exchange Server 2010 Test 70-663 Exam 070-663 QA PDF+SIM

US $6.97

27d 8h 43m

Microsoft Exchange Server 2010 Best Practices (2010,...

US $29.99

8d 2h 50m

NEW - Mastering Microsoft Exchange Server 2010

US $18.08

6d 2h 10m

Symantec Backup Exec 2010 R3 w/ 4 agents SERVER/SQL/EXCHANGE/ACTIVE DIRECTORY

US $1,500.00

16d 14h 42m

NEW Microsoft Exchange Server 2010 Standard Edition - 6

US $1,151.99

20d 18h 33m

MCTS 70-662 Exchange Server 2010 Configuring Exam 070-662 Test QA PDF+Simulator

US $6.97

9d 7h 53m

Microsoft Exchange Server 2010 Configuring 70-662 Exam Test Simulator & PDF

US $5.97

26d 11h 40m

Microsoft Exchange Server 2010 Administration Insta...

US $26.24

29d 10h 36m

Microsoft Exchange Server 2010 NEW by Siegfried Jagott

US $48.91

29d 11m

Microsoft Exchange Server 2010 Inside Out NEW

US $49.42

29d 11m

Powered by phpBay Pro

Users are reporting that after logging into the web interface they receive the following error when trying to launch an application, "An error occurred while making the requested connection." After logging in to the Xenapp Licensing server you notice that the Citrix licensing service is stopped. When you try to start the service you receive the following error, “Could not start the Citrix Licensing Service on Local Computer. Error 1067: The process terminated unexpectedly." The event log is that  lmadmin.exe is failing under Event ID 1000.

Citrix Licensing Service Will Not Start

At first, when I started troubleshooting this issue I was searching for the message, "An error occurred while making the requested connection." I came across this article that says to modify the WebInterface.conf file in order to resolve the issue. After making this change the error continued to show up and users could not launch any applications from the web interface. Looking at the services I noticed that the Citrix Licensing service was stopped. I tried many times to get the Licensing service to start, adjusted the recovery options to restart the service, but nothing would work. I also rebooted the licensing server which has cleared up similar issues in the past but the Licensing service was still failing. After doing some research everyone was pointing to this article on the Citrix Knowledge Center. I tried to follow the steps by moving the .lic files out of the licensing folder, but this article was written for an older version and some of the services mentioned did not exist. After over an hour of troubleshooting I decided to un-install and re-install the Citrix Licensing Management Console. Once this was complete I checked the licensing service and it was not started. I tried to access an application from the web interface but was still getting the error. I had log in to MyCitrix account and download the license file again and import to the License server. Went back to the web interface and successfully launched an application.

Resolution

This ultimately ended up being an issue with the Citirx License Server. The steps I took to resolve are as follows:

1. Re-install the Citrix Licensing Management Console.
2. Download your license file from your MyCitrix account.
3. Import the license file through the Licensing Management Console

When attempting to install Autocad Lt 2009 Updates you receive error 1625. This occurs when installing any updates including Update 1, Update 2.01, and Update 3. This issue has also been reported on other versions of Autocad including 2010.

Solution: Login  as the User who Installed Autocad

This problem can be resolved by logging in as the original user who installed Autocad  and running the updates. Installing the updates using the credentials of a user with local administrator privileges will still result in the error. After logging with the credentials of the user who installed Autocad the updates should complete successfully.

The updates to Autocad are supposed to help with unexpected crashing of the program and overall stability. After installing the updates we noticed that Autocad became much more stable with less unexpected freezes.

After Installing a Windows 7 VM on VMware Server 2.0, you do not have network access and no network adapter is present.

Install Windows 7 On VMware Server 2.0

I installed a Windows 7 VM, but because VMware does not officially support Windows 7 yet, it does not show up as on option under the guest Windows OS choices. I was not sure which option to choose so I proceeded with the install using Other as the OS. After choosing the hardware configuration the install started and seemed to finish just fine without any errors. The VM came up and everything looked good until I tried to get on the network. I was not getting and IP address and there was no network adapter present. I had other VMs working just fine so I knew there was no problem with the network configuration. After a little bit of research I found out that VMware Tools was not installed because I did not select one of the pre-configured choices for guest OS. I tried to do a manual install of VMware Tools and it failed.

Install VMware Tools – Workaround

I removed the previous VM and decided to do a clean install, but with one change to the configuration. I selected Windows Server 2008 as the Guest OS. The reason is that when you select  one of the existing guest OS choices VMware Tools is installed by default. The rest of the install was the same as before and completed successfully. When the VM powered on this time it had a network adapter present and I could access the network just fine. The only difference in this install was choosing Server 2008 at the beginning in order to install the VMware Tools automatically. Hopefully VMware will soon add native support for Windows 7.

<table cellpadding="0" cellspacing="0" border="0"><tr><td><img src="http://www.confighelper.com/images/0/" /><td></tr><tr><td><td></tr></table>,

The tool is now installed and can be accessed from Active Directory Users and Computers snap-in. When you view the properties of a user there will now be a new tab called Additional Account Info.

When you click on the tab, you will see a ton of information that was not previously available, at least not easily available. The fields you will see are Password Last Set, Password Expires, whether the account is currently locked out or not, Last-Logon-Timestamp, SID, GUID. You will also see the Last Logon and Last Logoff time, the Last Bad Logon time, the number of times that user has logged onto the domain under Logon Count, and then the current Bad Password Count. Keep in mind that the Bad Password Count will reset according to the password policy in effect on the domain. Also, if you click the Domain PW Info… button you will see the Domain Password Policy.

There is a great deal of information available with this utility and it is great for tracking down annoying lockout issues. Using the Last Bad Logon information, you can think about what scheduled tasks might be running at that time that is using a certain account with an old expired password, possibly a service account running a scheduled job. Hopefully you found this information useful and please take time to review our other articles. Additionally, if this article has helped you then please feel free to link back to it or to the ConfigHelper site.

<table cellpadding="0" cellspacing="0" border="0"><tr><td><img src="http://www.confighelper.com/images/0/" /><td></tr><tr><td><td></tr></table>

You have just installed VMware Server 2.0 for the first time and are trying to login and do not have the Login Name and Password.

Solution

VMware Server 2.0 is entirely web-based and no longer uses the familiar VMware 1.0 desktop application to manage the server. VMware Server 2.0 uses an existing account from your local OS install (i.e. Windows XP, Windows Server 2008, Linux, etc.) or your domain account. Note: If you are using a domain account you must enter the domain name before the username or the login will fail (i.e. domain\username).

XenApp Platinum 6.0, Windows Server 2008 R2

PROBLEM

After installing XenApp you run Discovery and receive the following error message: “Errors occurred when using Servername in the discovery process.”

Double-clicking the error message to see the error details reveals the following:

“An unexpected error occurred. Check that the server name is correct, that the server is on, that Citrix Presentation Server is installed on this server, and that the Citrix MFCOM Service is running.”

RESOLUTION

I followed the instructions on the Citrix forum to Enable Network COM+ access, and tried to run the discovery process but again received the same error message.

I realized that XenApp had been installed on the system with a local admin account, but the server was recently joined to a domain. I then un-installed XenApp, rebooted the server, then re-installed XenApp using an admin account that was part of the domain. (Citrix recommends that if you un-install XenApp, that you do not install it again until you have a freshly imaged server. This was in a test environment so I ignored these instructions, but did not have any problem after re-installing). After installing XenApp with the domain administrator account I ran discovery again the process completed successfully.

Note: As I later learned, XenApp 6.0 differs from 5.0 in that you do not need to pre-install the Windows roles, the installation will take care of that for you. If you are installing XenApp 6.0 on Windows Server 2008 R2 for the first time, you should be able to run the Citrix installation with out pre-installing the roles as you would with 5.0