Active Directory Users and Computers Snapin Error on Windows 2003 64 bit Domain Controller

Last night, I built a Windows 2003 64 bit server to act as a Branch Office Domain Controller and DFS File Server for a network with sites running Windows 2008 Server DCs. After installing Service Packs and patching the x64 Domain Controller, I ran dcpromo and installed DNS and Active Directory. After reboot, Active Directory Users and Computers snapin failed with the following error:

Snapin Error
MMC has detected an error in a snap-in. It is recommended that you shut down and restart MMC.

Active Directory Users and Computers MMC snap-in allowed the opening of one object but then crash when opening a 2nd object :( Close the dsa.msc snapin. Open the dsa.msc snapin. Same behavior every time.

After completing some research, the Snapin Error relates to schema differences between the Windows 2008 Domain Controller and the Windows 2003 64 bit Domain Controller. According to Microsoft, the cause is a follows:

This problem occurs because the Adsiedit.dll module uses an uninitialized pointer. When the system frees this pointer, some random data is freed. Therefore, an access violation may occur.

Microsoft released a hotfix for the issue:

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

In my particular case, Adsiedit.dll was updated to file version 5.2.3790.4277 by the hotfix. All good after that :)

Windows Server 2003 with Service Pack 2, x64-based versions
File name    File version    File size    Date    Time    Platform
Adsiedit.dll    5.2.3790.4277    616,960    22-Apr-2008    16:41    x64

For the community.
Hope this helps,
Mark
WIGITAL

1 Comment

Nuance DigiDocFlow Java Client Xlet Manual Installation on Ricoh MFP

In working with Document Solutions at WIGITAL we’re required to come up with a few “work-arounds” from time to time. Such is the case today with DigiDocFlow, a Document Management Solution we deploy in partnership with ImagingPlus.

Nuance DigiDocFlow is designed to auto-locate multi-function Print/Scan/Copy/Fax devices on a network and once selected, automatically bind with them. Next the DigiDocFlow Server can install a middle tier Java Client app extending the functionality of the MFP to integrate directly with DigiDocFlow. Two way communication between the 1.) DigiDocFlow Server and 2.) the Multi-Function device enables all sorts of “auto-magic” functionality. Today however (and unfortunately), the Automated Scan and Locate feature is not working. In short, our DigiDocFlow server cannot find some of our MFPs on the network.

Normally we’d attribute this to a network switch and or firewall potentially blocking traffic (they use lots of them at this particular customer) or the functionality potentially being turned of on the devices. So we examined that first. The MFPs all checked out OK. Next, as the DigiDocFlow Server is designed to locate the MFPs via SNMP, we needed to confirm SNMP traffic was allowed from the server to the MFP devices. I used PortQuery and verified SNMP was listening on the MFPs. It was. I then verified traffic was allowed from the DigiDocFlow Server to the MFP. Verified = YES. MFP Listening = ABSOLUTELY (confirmed).

A support call to Nuance yielded a “We’ve seen that before but we don’t actually know why it happens”. So I requested a support ticket be opened with them anyway and asked Nuance to take a closer look “for everyone’s benefit” in the future.

So, In the meantime, until Nuance sorts it out… here is the work-around to manually install the DigiDocFlow Java Client onto a Ricoh MFP and then get the MFP and DigiDocFlow Server talking.

Determine the DigiDocFlow Java Client Version For JavaTM Platform Version

The first thing we have to do is determine “what version” of DigiDocFlow client we should be trying to install onto the Ricoh MFP. The Java Client version required is determined by knowing what JavaTM Platform version is on the SD Card included with the Ricoh MFP. To get this information, please complete the following.

Access the target MFP using Web Image Monitor (i.e. your web browser pointed to the IP Address of the device)

Ricoh Web Image Monitor

Login as the admin user on the MFP

Ricoh Web UI Login

Select Configuration from the left column navigation

Ricoh MFP Configuration Page

  • Scroll to the bottom of the Configuration Page.
  • On the bottom right hand side are the Extended Feature Settings.
  • Click on the link Extended Feature Info
  • Under the Extended Feature Name column of the table, find JavaTM Platform

Ricoh MFP Extended Feature Info

The JavaTM Platform will list important information about the Extended Software Architecture on the MFP that we need to know. The following details are important:

  • The “Type” of the SD Card installed in the MFP (in our case Type C)
  • The “Status” ( Stop, Starting Up, Suspend, etc… )
  • The “Version” ( in our case 7.09.03 )

Each JavaTM Platform version has a corresponding Java Client ( sometimes referred to as Xlet ) that must be installed on the MFP for the Java based Extended Software Architecture to communicate with the specific platform your asking the MFP to integrate with.

In our install, the JavaTM Platform “version 7.09.03” requires Java Client version 4.x. Earlier versions of the JavaTM Platform. As of today, 2011-06-22, there are three Java Client versions

  • 1.x
  • 2.x
  • 4.x

** Please contact Nuance and/or Ricoh for information about specific Java Client to Java Platform version compatibility for your Ricoh device.

Prepare the DigiDocFlow Java Client For Installation

Once the Java Client version has been determined, you can logon to the server and build the package needed for installation onto the MFP.

By default, the Java Client applications for DigiDocFlow are located in the DigiDocFlow installation folder on the Server.

The default path is: C:\Program Files\Nuance\DigiDocFlow\Jar

Inside the Jar folder are the three Java Client versions

DigiDocFlow Java Client Versions

In our case we need version 4.x to match our JavaTM Platform

* Right click the folder 4.x
* Select Send To > Compressed (zipped) folder
* Choose a target location for the zipped 4.x Java Client that is accessible by your web browser (if needed) and .zip the file.
With a confirmed correct Java Client version to .zipped (compressed), we are now ready to manually install the Java Client ( Xlet ) on the Ricoh MFP

DigiDocFlow Java Client .zip

Install the DigiDocFlow Client Manually on Ricoh MFP

  • Using your Web Browser:  go back to the http:// web interface for your Ricoh MFP (Web Image Monitor ).
  • Login to the interface
  • Select Configuration from the left navigation
  • Locate Extended Feature Settings ( bottom right )
  • Select Install

Ricoh Extended Feature Settings Install

The install page will allow you to [Browse] to a Local File. Select the ( ) Local File radio button, and [Browse] to the location of your zipped Java Client package

DigiDocFlow Java Client Upload

Ricoh Install Local File Browse

Ricoh Display Extended Feature List

Now select the [Display Extended Feature List] button

This will unpack the contents of the .zip file and re-post the web page. The new web page loads the parameters that must defined when installing the Java Client. These parameters are:

  • Installation Target Setting ( what SD Card in the MFP to install the feature on )
  • Type-J Setting ( whether the feature should Auto Start – ON or OFF )
  • Extended Feature Lists ( radio buttons defining the exact feature to install )

DigiDocFlow Java Client Installation Target Setting

IMPORTANT: It is important to install to the correct SD Card Slot (see next section on “How To Find SD Card Slot Number”).

  • Install To – select the appropriate SD Card Slot from the drop down
  • Select Auto Start = ON
  • Select DigiDocFlow from the Extended Feature Name.
  • Click Install to install the feature.

How to find which Java SD Card Slot Number the JavaTM Platform is Installed on

In the above section, we explained how to install the Java Client. However, it is important to know which of the SD Card slots the Java Client should be installed on. It must match the SD Card that teh JavaTM Platform resides on. Here’s how:

  • Use http to access the Web UI of the Ricoh MFP
  • Login
  • Select Configuration from the left navigation
  • Scroll to the bottom of the Configuration Page.
  • On the bottom right hand side are the Extended Feature Settings.
  • Click on the link Extended Feature Info
  • You will notice a small icon (like Table of Contents or a List) next to the Extended Feature Name column
  • Hover your mouse over the icon, and you should see a Details pop-up
  • Click on the Icon next to JavaTM Platform

Ricoh Extended Feature Info Details

Among the Extended Feature Info Details is the “Startup Location” of the JavaTM Platform.

PLEASE NOTE THE FOLLOWING SCREENSHOT… Startup Location : SD Card Slot 2

Ricoh SD Card Slot Start Up Location

To review, Ricoh MFPs generally have two SD Card slots in which to add functionality to the MFP. !!! The JavaClient must be installed on the same SD Card that the JavaTM Platform is installed on ( this is per Nuance Customer Support ) !!! In our case the JavaTM Platform is installed on SD Card Slot 2 . Therefore, we must install the DigiDocFlow Java Client onto the same SD Card using Slot 2.

Please use this procedure for the above section. Thank you.

Defining the DigiDocFlow Server IP Address from the Ricoh MFP Front Panel

The next series of steps take place directly on the Ricoh Multi-Function device.

When manually installing the DigiDocFlow Java Client, it is necessary to also define the IP Address of the DigiDocFlow Server directly on the Ricoh MFP Device. To do so, complete the following steps from the front panel of the MFP.

Please note, the DigiDocFlow Client must already have been installed (per the previous steps) prior to completing this procedure.

  • Go to the Ricoh MFP
  • Press the Other Function Button
  • Select Settings
  • Select Password
  • Enter password: 14401 (this is the Ricoh default)
  • Select OK
  • Select IP Address
  • Enter the IP Adress of the DigiDocFlow Serer ( example 192.168.1.100 )
  • Select OK
  • Select OK

The Ricoh MFP is now programmed with the IP Address of the DigiDocFlow Server and ready to be added to the list of DigiDocFlow Scan Devices in the server software.
Manually Adding a Ricoh MFP to DigiDocFlow Server Software by IP Address

Add MFP Scan Device to DigiDocFlow Server

Please note, these steps are accomplished by launching DigiDocFlow on the Server and using the software interface.

Launch DigiDocFlow

DigiDocFlow Server Software

  • Stop the DigiDocFlow Service
  • Right-click on Scan Devices
  • Select Add

DigiDocFlow Add Scan Device

On the Scan Device New page

  • Select the Device [tab]
  • In the Scan Devices section, click in the IP Address / Host Name field
  • Enter the IP Address of the Ricoh MFP onto which the Java Client was just installed and mapped to this server
  • Select the Templates [tab]
  • Add at least one DigiDocFlow trigger/template
  • Click the OK button at bottom

DigiDocFlow Scan Device IP Address

IMPORTANT

When you click OK to add the MFP, you will be prompted to install the client on the device. Click NO as the Java Client was installed manually in this case  ”the reason for this article” :)   and is already on the device.

DigiDocFlow Install Java Client on Device Prompt

You should be given a “configuring devices” pop up briefly and setup will be completed.
Go to the MFP, select Other Functions, select DigiDocFlow, and “Refesh” the MFP. All new Templates should now be on the device.

At this point the DigiDocFlow Client is installed on the MFP, the MFP has been informed of the IP Address of the DigiDocFlow Server, and the Server has been informed of the IP Address of the Ricoh Multi-Function device. This completes manual setup.

Thank you and happy scanning :)

= = = =

For the community.
Hope this helps,
Mark
WIGITAL

No Comments

Windows 2008 hangs at Applying Computer Settings and Applying User Settings

As described in this post, recently I faced an issue in not being able to boot a Hyper-V virtual machine running Windows Server 2008 SP1. The VM would continually hang on Applying Computer Settings (or) if it got through that part of boot, was still hanging in Applying User Settings.

These articles helped resolve the issue:

In my case, the Service Control database was locked! To query the SC database for it’s status, open a command prompt and type sc querylock

sc querylock

The output below would indicate that the SCM database is locked:

QueryServiceLockstatus – Success
IsLocked : True
LockOwner : .\NT Service Control Manager
LockDuration : 1090 (seconds since acquired)

To resolve:

  1. Click Start, type regedit in the Start Search box, and then press ENTER.
  2. If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.
  3. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
  4. On the Edit menu, point to New, and then click Multi-string Value.
  5. Type DependOnService, and then press ENTER.
  6. Right-click DependOnService, and then click Modify.
  7. In the Value data box, type CRYPTSVC, and then click OK.
  8. Exit Registry Editor.
  9. Restart the computer.

Hope this helps,
Mark

1 Comment

Removing Hidden Physical and Virtual Network Adapters with DevCon

Recently I faced an issue in not being able to identify and view hidden network adapters with a Hyper-V virtual machine running Windows Server 2008 SP1. The VM was failing to boot and would continually hang on Applying Computer Settings (or) if it got through that part of boot, was still hanging in Applying User Settings.

As the VM would boot into Safe Mode with Networking, I started there and after digging around a bit, it appeared that the network adapters might be part of the issue. Ultimately it was one of two failures that, once resolved, allowed the VM to boot.

These two articles helped remove the adapters:

To be specific, the first method offered in KB269155 did not work as the adapters “remained hidden” even after using devmgmt.msc View > Show Hidden Devices. The only method successfully allowing access and removal of the Virtual Network Adapters was to use DevCon. DevCon is available for download from Microsoft and pros in the community here:

Please note, on 64bit Windows Server 2008 you must use the x64 (64bit version) of DevCon. The 32bit version will install, and you can run the commands, but it will not remove the adapters. The 64bit version will :)

Hope this helps,
Mark

2 Comments

Move WSUS Update Content and SUSDB Database in SBS 2008

Microsoft Small Business Server 2008 utilizes a Server Storage Management Tool to relocate WSUS Update Content from a given storage path to another storage path ( usually on a different volume / physical drive ) on the server.

Server Storage Management in Small Business Server 2008 is described here: Introducing Server Storage Management in SBS 2008

However, the SBS 2008 Server Storage Management Tools do NOT move the SUSDB Folder and the WSUS database which contains the metadata supporting WSUS. This data is (by Microsoft’s design) located on the WINDOWS SYSTEM DRIVE and can contribute to a Server running out of drive space and loosing functionality. As the WSUS SQL database can become quite large (i.e. multiple GBs), it’s critical to be able to move these database files.

The Official SBS Blog outlines how to move the SUSDB metadata .mdf and .ldf here: How to Move WSUS Content and Database Files to a Different Volume

Be aware that you will need to stop the services accessing SUSDB prior to detaching and moving the files. This is necessary prior to using SQL Server Management Studio Express and is not mentioned in the articles section relating to accessing the SUSDB SQL Database located at:


\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

These commands are:

NET STOP "Update Services"

NET STOP W3SVC

then Follow the SBS Blog Article relating to SQL Server Management Studio Express

NET START "Update Services"

NET START W3SVC

WSUSUTIL.exe

More WSUS objectives can be accomplished from the command line using the tool wsusutil.exe . A basic introduction to wsusutil.exe in the context of moving WSUS content can be found in these articles:

WSUS: How to change the location where WSUS stores updates locally

How to move your SUSDB (WSUS)

wsusutil.exe provides significant additional functionality above the GUI based tools offered in SBS 2008.

TechNet provides greater detail on wsusutil.exe here:

Managing WSUS from the Command Line

SBS 2008 Server Storage Move Data Wizard Troubleshooting

Some SBS 2008 Installations may fail to successfully move the WSUS Content via the Small Business Server 2008 Storage Management Tools. When attempting to move Server Storage with the move data wizard the following failure message may appear!

Windows SBS 2008 Move Data Wizard has stopped working

This message is highly “non-descript” and the EventLog’s offer little additional data as to resolution. Here is a full copy of the available error data.

Windows SBS 2008 Move Data Wizard has stopped working

Description:
  Stopped working

Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	movedata.exe
  Problem Signature 02:	6.0.5601.0
  Problem Signature 03:	48a22618
  Problem Signature 04:	mscorlib
  Problem Signature 05:	2.0.0.0
  Problem Signature 06:	4be9036a
  Problem Signature 07:	20c7
  Problem Signature 08:	143
  Problem Signature 09:	N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
  OS Version:	6.0.6001.2.1.0.305.9
  Locale ID:	1033

Read our privacy statement:

http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

If this occurs, the above articles on the command line WSUS Utility can help achieve the goals of moving the WSUS Content without employing the SBS 2008 Server Storage wizard(s) to the move the update content  :)

Look specifically for help on movecontent

wsusutil.exe help movecontent

The default path to wsusutil.exe is C:\Program Files\Update Services\Tools\wsusutil.exe

Hope this helps,
Mark Raborn

, , , , ,

No Comments

Exchange 2007 Public Folder ADSI Heirachy Causes Outlook Failure Cannot Connect

This week, we were on a service call to support an Outlook client connectivity issue with Exchange Server 2007. The error message was basically telling us that this Earlier Outlook client cannot connect to Exchange 2007 Server.

Search queries offered the following:

The second linked KB article above offered these potential causes:

  • You do not have an existing public folder tree.
  • MAPI is disabled for your mailbox.
  • Cached Exchange Mode is required for your mailbox.
  • RPC/HTTP mode is disabled for your mailbox.
  • Your version of Outlook is specifically blocked by Exchange 2007.

Our issue appeared behind door number ONE. Exchange could not properly enumerate the Public Folder Tree because elements and attributes were missing in Active Directory Services Integration. This missing data caused Exchange 2007 to return errors relating to the (1.) Public Folder Database AND (2.) Public Folder Tree as we worked through Troubleshooting the issue.

At first, because the PublicFolderDatabase.edb “was indeed present” in the following path:

E:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group

we thought we’d access the Properties and review the state and settings of the database, confirm it was properly mounted, etc…. When we attempted to access the properties, we received the first error intimating that the PublicFolderDatabase.edb was corrupted (an error which was itself “in error” as later, when we were able to re-mount it, the PublicFolderDatabase.edb performed as healthy).

Exchange Public Folder Error 1

--------------------------------------------------------
Microsoft Exchange Warning
--------------------------------------------------------
The following warning(s) were reported while loading topology information:

get-PublicFolderDatabase
Completed

Warning:
Object YOUR-SERVER\Second Storage Group\Public Folder Database has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
PublicFolderHierarchy is mandatory.

Warning:
PublicFolderHierarchy is mandatory.

--------------------------------------------------------
OK
--------------------------------------------------------

Since we knew this particular client did not actually use Public Folders in any capacity, we elected to DELETE the Public Folder Database (since there was no data in it) and re-create it.

NOT SO FAST EXCHANGE SERVER SAID !  After making the attempt to delete the PublicFolderDatabase.edb, we got a second error stating that a critical property ‘PublicFolderHierarchy’ is missing in the PublicFolderDatabase. This error essentially would not allow us to delete.

Exchange Public Folder Error 2

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
The public folder database 'Public Folder Database' cannot be deleted.

Public Folder Database
Failed
Error:
The critical property 'PublicFolderHierarchy' is missing in the PublicFolderDatabase object 'YOUR-SERVER\Second Storage Group\Public Folder Database'.

--------------------------------------------------------
OK
--------------------------------------------------------

In the end, after a lot of Question and Answer…. what turned out to be true for this client was a historical event:  “a migration from Exchange Server 2003 to Exchange Server 2007″ that had gone a little wrong. Since the client did not use Public Folders, they had elected not to Migrate them, thinking it was not necessary since they were not actually used.

What resulted from this, and the attempted later clean up effort using ADSI Edit, were missing elements and attributes in Active Directory Services Integration.

This post on Social.Microsoft.com enabled us to provide a solution. The solution (as quoted from SONNY1 at Social.Microsoft) follows:

Restoring Public Folder Hierarchies to Exchange Administrative Group using ADSI Edit

Open adsiedit.msc.

Select Configuration-Configuration-Services-Microsoft Exchange-Orgname-Administrative Groups-Exchange Administrative Group.

Now we were missing the ‘Folder Hierarchies’ folder – how I still am unsure of. All we had to do was recreate it as follows:

Create the “Folder Hierarchies” under the Exchange Administrative Group

  1. Right click on Exchange Administrative Group
  2. Select New Object
  3. Select msExchPublicFolderTreeContainer for the class and click Next
  4. Enter the following for the value: Folder Hierarchies, click Next
  5. Click Finish

Create Public Folder Tree Object

  1. Right click CN=Folder Hierarchies -> New Object
  2. Selected msExchPFTree for the class
  3. For the value we entered, “Public Folders” and clicked next
  4. Clicked on the “More Attributes” button, selected msExchPFTreeType and set the value to 1. Note: This is very important that this value is set to a value of 1 as this tells Exchange that this is a MAPI Tree
  5. Click Ok and then finish

Populate msExchOwningPFTreeBL attribute object of the PF Stores in the organization

(Since this attribute is not directly editable, you have to follow the below steps to do this for each PF store)

  1. Get properties of the newly created “Public Folders” Tree object in ADSIEdit.
  2. Copy the distinguishedname value to the clipboard and then click cancel.
  3. Navigate to the Storage group that contains the Public Folder Store for this server and get properties of the server.
  4. Locate the msExchOwningPFTree attribute and paste in the value that was copied to the clipboard in step 2. Click OK.
  5. Restart the Information Store Service
  6. Now try to mount the PF store and see if we can access it fine now.

As soon as the Information Store starts, remount the PublicFolderDatabase.EDB using the Exchange Management Console.

WIGITAL would like to thank Sonny1 for the valuable insights.

Sonny1′s original reply is posted at – - Public Folder database wont mount on a CCR cluster

Thank You

Hope this helps you as well.

Mark Raborn
WIGITAL

, , , ,

6 Comments

Google sync Contacts Calendar and Gmail to Microsoft Outlook

PAY

Google Apps Calendar Contacts Gmail Sync With Outlook

$ Requires Google Apps Premiere Account

$50 per year

http://www.google.com/apps/intl/en/business/index.html

http://www.google.com/apps/intl/en/business/outlook_sync.html

Sync’s Calendar and Contacts

http://www.google.com/sync/pc.html

http://mail.google.com/support/bin/answer.py?answer=171747

http://mail.google.com/support/bin/answer.py?hl=en&answer=156587

Google Contacts and Calendar Sync with Outlook

KiGoo

$9.95 a year

http://www.getkigoo.com/

http://www.mydigitallife.info/2008/08/12/synchronize-ms-outlook-and-google-calendargmail-with-free-sync-utility-kigoo/



FREE

Google Calendar Sync with Outlook

Knokio

http://www.google.com/support/calendar/bin/answer.py?answer=89955

http://knokio.com/guide/sync-gmail-contacts-and-google-calendar-with-outlook/

Google Contacts Sync with Outlook

GContactSync

GoogleCode Contact Sync (in BETA)

http://code.google.com/p/gcontactsynch/

http://www.blogsdna.com/5191/sync-gmail-contacts-with-outlook-using-google-contacts-outlook-synchronizer.htm

GoContactSync

GoContactSync (Open Source)

http://sourceforge.net/projects/gocontactsync/files/

http://www.webgear.co.nz/Products/GOContactSync.aspx

Other Sync Options

CompanionLink

A company to know about is CompanionLink. They are the Swiss Army Knife of Sync and have options for a number of different devices, components, and platforms. Check them out at

http://www.companionlink.com/

, , , , , ,

No Comments

Service RunAs Accounts in System Center Essentials

RunAs Accounts in SCE 2007

Service Accounts in System Center Essentials are added to Active Directory Users and Computers as Domain User accounts (and sometimes Local Accounts). This precept is similar to other Server Applications or Line of Business Applications where dedicated accounts are required to perform services and tasks across a network. The privileges for these accounts vary by role and the type of deployment topology chosen for System Center.

System Center Essentials uses the following two topology categories:

  • Local – Single Server
  • Distrbuted – Multiple Servers for Management, SQL Database Instance, SQL Reporting Services, and SCE Console

In System Center Essentials, Service Accounts are referred to as RunAs Accounts and are defined in the System Center Administration Console.

  • Launch System Center Essentials
  • Select Go | Administration
  • In the Navigation Pane, under Administration, open the Security node, and click RunAs Accounts
  • In the details pane on the right, you can view the RunAs Accounts (which are the Service Accounts) for System Center Essentials

The default RunAs Accounts ( Service Accounts ) in System Center Essentials are as follows:

Action Account
This is the user account under which all rules run by default on the agent. There are two Agents deployed in System Center Essentials: the Management Agent, and the Update Agent.

Data Warehouse Account
If specified, this account is used to run all Data Warehouse collection and synchronization rules instead of the default action account. If this account is not overridden by the Data Warehouse SQL Server Authentication account, this account is used by collection and synchronization rules to connect to the Data Warehouse databases using Windows integrated authentication.

Execution Account
This account is used by SCE 2007 in accessing SQL Reporting Services.The execution account allows the report server to perform unattended operations at a very low security level. Some functionality is disabled if an account is not specified..

For a full explanation of RunAs Accounts in System Center, read

To learn about configuring an Execution Account in SQL Reporting Services, read

SCE 2007 in EBS 2008

System Center Essentials 2007 is also included in Essential Business Server 2008. The deployment practices of SCE 2007 on EBS 2008 are unique. To learn more about how the default Administrator Account is used in System Center Essentials on EBS 2008, please read EBS Administration Console Returns “Monitoring Data Not Available” After the Administrator Account Password is Changed or Expires. This article discusses issues in the default architecture and how to address them.

Service Pack 1 for System Center Essentials 2007

The installation of SP1 for SCE 2007 resolves a number of issues on deployment, with Agents, and so on. Install SP1 prior to assigning service RunAs accounts or beginning discovery on your network.

You can download System Center Essentials 2007 Service Pack 1 (SP1) as well as learn more about SP1 here.

Determining if System Center Essentials Service Pack 1 is installed

In the Help menu of most Microsoft products, there is usually a menu item indicating the version and service pack of the software installed. In System Center Essentials, this is not the case. No product number, version number, or service pack is listed in About System Center Essentials.

You must open the registry to view the exact version number of SCE 2007

  • Go to Start | Run | type regedit
  • Navigate to HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\setup
  • View the KEY UIVersion. If the version number is 6.0.6278.0 then SCE Service Pack 1 is installed

SourceSCE SP1 installation error “no upgradeable SCE Product found

Thank You

Hope this helps you as well.

Mark Raborn
WIGITAL

No Comments

Joomla 1.6 ACL Access Control List Features Presentation

Andrew Eddie, original project manager for the Mambo project who’s August 2005 Letter to the Community heralded the eventual beginnings of Joomla, has run through the latest ACL implementation of Joomla 1.6 at the Melbourne Joomla Users Group meeting ( February 16th, 2010 ).

Videos and a PDF of the slides from that presentaton are embedded. Take some time to review these and familiarize yourself with the new ACL ( Access Control List ) features of Joomla 1.6.

Those of us who use and/or support Joomla should benefit from the MJUG meeting.

MJUG Joomla 1.6 ACL Presentation by Andrew Eddie
( Part 1 of 2 )

MJUG Joomla 1.6 ACL Presentation by Andrew Eddie
( Part 2 of 2 )

Joomla 1.6 Access Control List Slides

Joomla 1.6 Slide Presentation – Andrew Eddie – Core Developer – MJUG 2010-02-16

Joomla 1.6 Access Control List Articles

Andrew’s blog, the Art of Joomla, has a great article Introducing the New Permissions in Joomla 1.6. Worth a read.

Andrew Eddie is a co-founder of the Joomla Open Source project and is highly active in the version 1.6 development process. He currently operates a Joomla-based development and training consultancy New Life in IT, and produces high-quality commercial Joomla extensions through his sister company JXtended.

Joomla 1.6 Nightly Builds

If you are interested in pre-flighting the next release: download nightly builds of the upcoming Joomla 1.6 Beta from SVN at the Joomla Forge SVN

Thank You

Hope this helps you as well.

Mark Raborn
WIGITAL

, , , , , , , , , ,

No Comments

PayPal Plugins for Joomla

Joomla PayPal Extensions

For those interested in Plugins using simple syntax to enable PayPal Buttons in articles, there are PayPal plugins for Joomla. Search the Joomla Extensions directory for offerings.

For WIGITAL Customers that want to take a do it yourself approach from within Joomla and do not wish to leave the Administrator backend to get PayPal functionality, there are two commonly used Joomla PayPal plugins we suggest:

Easy Paypal by HyBing

http://extensions.joomla.org/extensions/e-commerce/payment-systems/2651

Nice Paypal by TriniTronic

http://extensions.joomla.org/extensions/e-commerce/payment-systems/9277

Using the Joomla PayPal Extensions

Turn Off the TinyMCE Editor

The Joomla Document library discusses using PayPal type extensions  in this post . The use of PayPal extensions require that HTML can be typed into web pages along with the specific code needed to interact with PayPal using PayPal’s API. The first consideration then, is to avoid the use of  the default TinyMCE Editor in Joomla. TinyMCE strips out certain forms of HTML on save, and since the PayPal API requires custom HTML and various propriertary syntax to function, you must not use the default editor. Read this post to turn off TinyMCE.

Sign Up for Business PayPal Account

Receiving PayPal payments requires a PayPal Business Account. Sign up to “Build Your Business Online with PayPal

For WIGITAL Customers, we suggest a dedicated PayPal email address and identitity in your environment. Whether in a Windows Domain and using Microsoft Exchange to receive notifications, or using an email service like Gmail, Hotmail, Yahoo Mail, etc… , having an identity dedicated to this function, “that is secure” and accessible only by Accounting and Management roles, is advisable.

  • Create an account / identity dedicated to the PayPal relationship
  • Sign up with PayPal Business

Easy PayPal Tutorial

http://www.hybing.com/Easy-Paypal-Tutorial.html

Nice PayPal Tutorial

http://www.trinitronic.com/index.php/Downloads/nice-paypal-button-documentation.html

Installing Joomla PayPal Extensions

Here are the steps to setup Nice PayPal ( as an example )

  1. If you don’t already have one, sign up for a business PayPal account.
  2. Install the plugin using Joomla’s Extension Manager.
  3. Go to Extensions>>Plugin Manager and click into the plugin “Content – Nice PayPal Button.”
  4. Enable the plugin.
  5. Add your PayPal account email to the parameters on the right.
  6. Optionally add your sandbox sellers account email if you plan to do testing.
  7. Optionally set the test mode to on or off – the default is off.
  8. Optionally enter your PayPal supported 3 letter currency code – default is USD.
  9. Optionally, Enter your 2 digit country code to set the language used on the PayPal payment page. PayPal uses a two-character country code (ISO 3166). Some examples are United States: US, Great Britain: GB, France: FR, Spain: ES, Poland: PL, German: DE. If you don’t know your country code, or you can Google PayPal Country Codes.
  10. Optionally, set your button language code. PayPal uses a 5 character code to designate language it’s buttons. For example, United States English is designated with en_US. Enter the 5 character code for the desired button language. Other code examples are Great Britain English: en_GB, French: fr_FR, Spanish: es_ES, Polish: pl_PL, German: de_DE. If you don’t know the code for your desired language, log into PayPal use the button creator and search the resulting HTML code for this https://www.paypal.com/en_US/i/btn/btn_buynow_LG.gif. Notice the en_US in the URL, it’s the language code for the button.
  11. Save your changes.
  12. Important – Email Cloaking is a default feature of Joomla. Unless you have specifically disabled it, it is enabled on your site. If this is the case then, in the Plugin Manager, you will need to change the order of the Nice PayPal Button plugin so that it appears below the Email Cloaking plugin in the plugin list. Otherwise, the PayPal buttons that the Nice PayPal plugin creates won’t work properly.
  13. Add the tag code {nicepaypal:button type|price|item name} to your article where you want the PayPal button to show up.

Place the Nice PayPal Button tag in your article content.

A PayPal button replaces the Nice PayPal button tag.

The PayPal Developers Site

For those interested in the DIY “Do It Yourself” approach that requires a little more investment than point-and-click in the Joomla back end, PayPal provides their API, development practices, documentation, sample apps, etc… at the PayPal Developers Network

An extraordinary amount of functionality can be achieved, integrated, and customized into your website using PayPal’s online tools. These tools require no knowledge of coding and can broaden website functionality with PayPal using simple cut and paste of code that PayPal generates on your behalf as you use their online resources.

In addition, you can go further as a developer.

Here are some important links ( and suggested reading )

, , ,

4 Comments