Until SteadyState is ready - question with WDP
If anyone has a solution to my big steadystate problem, I would love to hear it! I use Novell Zenworks to push down a domain policy. That policy never seems to make it on the computer or take effect. I have tried applying it to my public user with NO restrictions and also having the public user set as an administrator. No matter what I set, when I log in as the user, the domain policy doesn't get applied. Using the SCT, it works fine.
My SCT WDP problem is this: I have a workstation (Dell Optiplex GX520) with a 160gb SATA drive. I have removed all the partitions and re-imaged the drive. I now have two partitions: the primary (C
(140gb) and unused space (WDP partition) (20gb). I go through all the motions to setup WDP and I get to the point where it says that it is ready and I need to restart. When I restart, I run WDP again and it tells me that the drive doesn't currently support WDP! I've seem some stuff about the enhanced filter and i've read every document I can find. I cannot seem to make WDP work. Is it the SATA drives? Any ideas?matt (hoping that SS will soon have at least as much protection as the SCT. Why would MS release a product that protects less than the program it replaces?)
Reply:
Hi Matt,
I would like to give a brief summary of your concerns as I understand them.
1. Some Novell policies could not be applied properly.
2. SteadyState Windows Disk Protection (WDP) cannot be enabled.
If I have misunderstood, please feel free to let me know.
I am sorry that I am a little unclear as to the exact issue. To get more detailed background information, we need to clarify some questions.
Problem #1
----------------------
- Which product does it happen on, SteadyState or SCT?
- Have you enabled WDP?
- Which kind of Novell policy are you trying to apply?
- Can the policy be scheduled to apply on a specific time?
When Windows Disk Protection of SteadyState is on, software updates to the computer are ideally performed through the critical updates process offered by Windows Disk Protection. With Windows Disk Protection, software updates must be scheduled at specific times. For more information, please refer to the "Central Software Management and Windows Disk Protection" section of SteadyState handbook.
Problem #2
--------------
- Which product does it happen on, SteadyState or SCT?
- What is the exact error when you try to enable WDP and reboot the computer? Please let us know the error message WORD BY WORD.
If you are using SteadyState, please check the hard drive and then defrag it first as WDP is very sensitive to the hard drive physical layout.
Best Regards,
------------------------------------
Reply:
I think that I have also run into the same problem as Matt.
I have installed the Shared Computer Toolkit on about 30 PCs.
I had situations where some of the PCs would not activate the WDP.
In my situation I try to enable the WDP, the PC requests a reboot.
The problem is that after the reboot, the WDP is still disabled.
If I check the WDP control panel, it states something like: "WDP is not supported".
Regards,
------------------------------------
Reply:
Hi KS07,
Before getting a confirmation from Matt, I am not sure whether your situation is the same.
Please understand that this forum mainly focus on SteadyState related issues. The previous versions are not supported. If you need assistance on Shared Computer Toolkit, I suggest that you post to the Shared Computer Toolkit public newsgroup:
The reason why we recommend posting appropriately is that you will get the most qualified pool of respondents, and other customers who read the newsgroups regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
------------------------------------
Reply:
Is it moved to another loocation?
Could you point me to the new location?
Thank you,
------------------------------------
Reply:
Since the original newsgroup is not available now, you can post this request to the Windows XP General Newsgroup:
You can also update Shared Computer Toolkit to SteadyState. If there is any further problem, we can discuss together within this forum.
Regards,
------------------------------------
Redudant information is needed to documentation
One example:
I want to find out more information about ConfigMgr client's BITS settings. I search for BITS from ConfigMgr help file and first one in the topic list is: Computer Client Agent: BITS Tab.
When I go to this topic which is under Technical Reference, there is no mention that BITS settings are actually written to client's local policy and if you define those same BITS settings with GPOs, GPO settings would override ConfigMgr's settings. I think I've seen this warning in other parts of documentation, but I couldn't find it easily.
This GPO warning should be located at multiple places in documentation, because depending on how you search for documentation, you might end to different topics and you might not go to other topics. At least, the technical reference topics should have the most complete information about the item, because you go to technical reference if you click help button while you are defining any settings.
We have the same issue about network discovery and DHCP servers: technical reference should mention that only Microsoft DHCP server is supported.
Reply:
Thanks, Panu,
I've filed a bug about the BITS/GPO issue, but it's too late to get into this doc release. Should make it into the next one.
I already filed a bug about the DHCP servers.
Yes, we really are trying to put helpful information in the help topic.
------------------------------------
Welcome to the Forefront Edge Security Installation, Upgrade, and Setup Forum!
Welcome to the Forefront Edge Security Installation, Upgrade, and Setup Forum!
In this space you can post ideas, questions, or issues that you encounter when installing, upgrading or setting up ISA Server.
A broad range of IT professionals, Microsoft employees, and MVPs will take part in these discussions, which we expect to be interesting and helpful. We look forward to your participation.
Reply:
Nathan;
i just purchased isa 2006. i installed it and was unhappy with the client access response time when we request web pages from the internet. i tried again, but i am still not convinced i am getting the configuration correct. my first problem is that i cannot configure my allow rule using the built in networks internal and external. i must use all networks or i don't get any access at all. i would like to start with this problem and then move on to creating a rule that restricts all access to certain ip address's. finally i still have the issue of sluggish response when my clients use the internet.
thanks
rick
------------------------------------
Reply:
Hi Rick,
in order to create a rule to access the internet, for HTTP and HTTPS for example, it needs to look something like this:
From: Internet
To: External
Protocols: HTTP, HTTPS
Users: All Users
That will give you a basic outbound access rule.
Then, within that rule in your destination or TO tab, you can create a list of IP's/Domains/URL's which can be an exception to the rule, in which case access to those IP's will be denied. I would also suggest that you turn on authenticcation for a browsing rule, makes it easier to track who is doing what from a logging point of view.
Let me know how it goes!
Dave.
------------------------------------
Reply:
i tried your example above. if i try to use the internal network in the from tab and the external network in the to tab, i get no access. the only way i get access is to use all networks in the from tab and all networks in the to tab. then i have access.
i think this is a problem i need to resolve. i have tried several things that have not worked. do you have any suggestions?
rick
------------------------------------
Reply:
Firstly, lets discuss how your isa is setup.
Do you have 2 nics?
The internal network is everything you should define as 'behind' the isa firewall, external represents everything that is not defined. the problem with the way you have made it work is that it is basically an any <-> any rule, which is obviously not a good thing from a security point of view.
In my opinion, there is something wrong one of two things.
1. either your internal network is not defined correctly.
2. you have somehow changed your NAT rules.
But lets discuss further once you have mentioned your ISA setup.
Thanks,
Dave.
------------------------------------
Reply:
i have 2 nic's. the internal network is setup with a range of ip addresses starting with 172.23.51.2 and ending with 172.23.51.254. the internal nic does not have any gateway or dns configured. the external nic has a public IP address, gateway, and dns server designations.
dave, is it possible to correspond through my company email address? its rlorentz@siimex.com . this would be better for me. i am also willing to do a live meeting if required.
thanks
rick
------------------------------------
SCE Installation
I have been attempting to install SCE 2007 on my server for the past few days and have not been successful.
It's a clean server with Sharepoint 2007 installed and running on it. I do NOT have any sharepoint directories extended to the default virtual site. Originally I had the default website stopped because I was using port 80 for sharepoint on a different site, however, I have remedied that and proceeded farther with the installation of SCE. I've tried all of the default options and I still recieve the same error. The only error I can find on the log is this: UnableToGetUserNameFromManagementServerActionAccount = SetPropertiesToManagementServerActionAndSDKAccountCA: Error: Unable to get the Management Server Action Account
I am using the domain administrator account. As well as I tried an account I created just for SCE with administrative privelegas. I recieved the same error either way. below I've pasted part of my log for review:
Property(S): ProgressDlg_Desc1 = The program components you selected are being installed.
Property(S): ProgressDlg_Desc2 = The program components you selected are being uninstalled.
Property(S): SelectFolder_Text = Select the installation folder.
Property(S): SummaryDlg_Title = Ready to Install
Property(S): MinimumUserPrivilegeMsg = This product requires administrator privileges to install.
Property(S): ManagementGroupErrDlg_Title = Invalid Management Group name
Property(S): ManagementGroupErrDlg_Desc = This problem occurs when the Management Group name is:
Property(S): ManagementGroupErrDlg_EmptyOrNull = - Empty or Null
Property(S): ManagementGroupErrDlg_LeadingOrTrailingSpaces = - Leading or Trailing spaces
Property(S): ManagementGroupErrDlg_AlreadyExists = - Already exists on this computer
Property(S): ManagementGroupErrDlg_SpecialChars = - Contains special characters. The Management Group name should not contain following special characters: ^@)~(:!`#%\*+$|,&&='["]/<.{;?>}
Property(S): ManagementGroupErrDlg_Help = To continue setup, go back and change the Management Group name.
Property(S): ActionsAccountDlg_Type1 = &Local System
Property(S): ActionsAccountDlg_Type0 = Do&main or Local Computer Account
Property(S): AccountVerificationErrDlg_Title = Account Verification Error
Property(S): AccountVerificationErrDlg_Text1 = Setup is unable to confirm the account details. For Operations Manager SDK account make sure it is a Local Administrator account.
Property(S): AccountVerificationErrDlg_Text3 = To continue setup, go back and enter the correct account information.
Property(S): User_Account = &User Account:
Property(S): User_Password = &Password:
Property(S): User_Domain = &Domain or local computer:
Property(S): User_Domain_Only = &Domain:
Property(S): AgentServerCompatibilityErrDlg_Title = Incompatible Management Server Found
Property(S): AgentServerCompatibilityErrDlg_Text1 = A different version of System Center Operations Manager was found on the system. Setup cannot continue.
Property(S): AgentServerCompatibilityErrDlg_Text3 = Click Cancel to exit the installation. Then, either uninstall or upgrade the Operations Manager components on this computer and restart setup.
Property(S): WrongPackage = This installation package is not supported by this processor type.
Property(S): SetupExitHelp_Text = To exit the installation, click Cancel.
Property(S): ReadyToInstall_DlgText_InstallText = Click Install to begin the installation.
Property(S): ReadyToInstall_DlgText_RemoveText = Click remove to begin uninstallation.
Property(S): ReadyToInstall_DlgText_UpgradeText = Click Upgrade to begin the upgrade.
Property(S): This_Computer = (this Computer)
Property(S): SummaryDlg_Help = If you want to review or change any of your installation settings, click Back. Click Cancel to exit the setup wizard.
Property(S): ManagementGroupInfoDlg_Title = Management Group Configuration
Property(S): ManagementGroupInfoDlg_Desc = Specify the management group information that is necessary for this computer to connect to.
Property(S): ManagementGroupInfoDlg_CfgLabel = Management &Group Name:
Property(S): ManagementGroupInfoDlg_ConsLabel = &Management Server:
Property(S): ManagementGroupInfoDlg_PortLabel = Management Server &Port:
Property(S): ManagementServerOrPortErrDlg_Title = Invalid Configuration
Property(S): ManagementServerOrPortErrDlg_EmptyMSOrAMS = The given Management Server name is invalid. None of the configuration fields can be empty.
Property(S): ManagementServerOrPortErrDlg_EmptyMSOrAMSHelp = To continue, go back and provide the Management Server name and Management Group name.
Property(S): ManagementServerOrPortErrDlg_SpecialChars = The Management Server name is either blank or contains special characters. The Management Server name should not contain the following special characters: (![[:^)]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_ugE_rodnYQSpWQjMZAISz6Gxv_axDPXVB3CsWSQ8Ni00EK45eRCplCYnBXa4wXYk7HlPuy1eGz0W2T-k7PylKjRtOS6FwdRiqfCUKBpKhjAgv0lhkCghN9dTDYEA=s0-d)
Property(S): ManagementServerOrPortErrDlg_SpecialCharsHelp = To continue setup, go back and change the Management Server name.
Property(S): ManagementServerOrPortErrDlg_Port = The Management Server port number is either blank or not in the range 1024-65535.
Property(S): ManagementServerOrPortErrDlg_PortHelp = To continue setup, go back and change the Management Server port number.
Property(S): AdminNetworkLocation_Browse = &Change...
Property(S): AdminNetworkLocation_DlgDesc = Specify a network location for the server image of the product.
Property(S): AdminNetworkLocation_DlgTitle = Network Location
Property(S): AdminNetworkLocation_DlgText = Enter the network location or click Change to browse to a location. Click Install to create a server image of System Center Operations Manager Agent at the specified network location or click Cancel to exit the wizard.
Property(S): AdminNetworkLocation_LBBrowse = &Network location:
Property(S): SetupError_FinishText1 = Your system has not been modified. To complete installation at another time, please run setup again.
Property(S): SetupError_RestContText1 = You can either keep any existing installed elements on your system to continue this installation at a later time or you can restore your system to its original state prior to the installation.
Property(S): SetupError_RestContText2 = Click Restore or Continue Later to exit the wizard.
Property(S): Progress_TextTime = )Hidden for now)Estimated time remaining:
Property(S): Progress_LbSec = (Hidden for now)Sec.
Property(S): Progress_LbStatus = Status :
Property(S): Progress_ShowTime = (Hidden for now)
Property(S): BrowseToDest_Text = Browse to the destination folder.
Property(S): BrowseFolderDlg_Combo = &Look in:
Property(S): BrowseFolderDlg_Tail = &Folder name:
Property(S): BrowseFolderDlg_DescData = Browse to the folder you want to create database data file in.
Property(S): BrowseFolderDlg_DescLog = Browse to the folder you want to create database log file in.
Property(S): BrowseFolderDlg_Title = Change Installation Folder
Property(S): BrowseFolderDlg_TitleData = Change Database Data File Folder
Property(S): BrowseFolderDlg_TitleLog = Change Database Log File Folder
Property(S): MOMInstallDir_Exists = Setup has detected an existing Operations Manager Agent or Operations Manager Server component. The Operations Manager component that is chosen will be installed to the existing folder.
Property(S): OutOfSpaceDlg_DlgDesc = Disk space required for the installation exceeds available disk space.
Property(S): OutOfSpaceDlg_DlgTitle = Out of Disk Space
Property(S): OutOfSpaceDlg_DlgText = The highlighted volumes do not have enough disk space available for the currently selected components. You can remove files from the highlighted volumes, choose to install less components onto local drives, or select different destination drives.
Property(S): DiskSpaceDlg_DlgDesc = The disk space required for the installation of the selected components.
Property(S): DiskSpaceDlg_DlgTitle = Disk Space Requirements
Property(S): PreReqNotMetDlg_PreReq_Recommended_Not_Met = The recommended prerequisites for installation have not been met. You may continue to install Operations Manager, but you might not achieve optimum performance. For more information, click View Log.
Property(S): PreReqNotMetDlg_PreReq_Not_Met = The mimimum prerequisites for installation have not been met. For more information, click View Log.
Property(S): PreReqNotMetDlg_PreReq_No_Component_Selected = No components have been selected for installation. To select components for installation, click Back.
Property(S): PreReqNotMetDlg_Title_PreReq_Recommended_Not_Met = Prerequisite Check Passed with Warnings
Property(S): PreReqNotMetDlg_Title_PreReq_Not_Met = Prerequisite Check Did Not Pass
Property(S): ReadyToInstallDlg_Desc = The wizard is ready to install Operations Manager 2007.
Property(S): ReadyToInstall_DlgTitle = Ready to Modify the Program
Property(S): ReadyToInstall_DlgTitle2 = Ready to Repair the Program
Property(S): ReadyToInstall_DlgTitle3 = Ready to Install the Program
Property(S): ReadyToInstall_DlgText1 = If you want to review or change any of your installation settings, click Back. Click Cancel to exit the setup wizard.
Property(S): FilesInUse_DlgDesc = Some files that need to be updated are currently in use.
Property(S): FilesInUse_DlgTitle = Files in Use
Property(S): FilesInUse_DlgText = The following applications are using files that need to be updated by this setup. Close these applications and click Retry to continue.
Property(S): ReadyToRemove_DlgDesc = You have chosen to remove the program from your system.
Property(S): ReadyToRemove_DlgTitle = Remove the Program
Property(S): ReadyToRemove_DlgText1 = If you want to review or change any settings, click Back.
Property(S): DestFolder_Text = Destination Folder
Property(S): AgreeToLicenseDlg_Desc = Please read the following license agreement. Press the PAGE DOWN key to see the rest of the agreement.
Property(S): AgreeToLicenseDlg_Title = End-User License Agreement
Property(S): AgreeToLicenseDlg_No = I &do not accept the terms in the license agreement
Property(S): AgreeToLicenseDlg_Yes = I &accept the terms in the license agreement
Property(S): MaintenanceDlg_Remove = Remove this product from your computer. Use this option to remove all SC components.
Property(S): MaintenanceDlg_Repair = Repair SC components that are already installed. Use this option to fix missing or corrupt files, shortcuts, and registry entries.
Property(S): MaintenanceDlg_Modify = Change which SC components are installed. Use this option to add or remove components.
Property(S): RootManagementServerDlg_Title = Connect to the Root Management Server
Property(S): RootManagementServerDlg_MGServer = &Root Management Server:
Property(S): RootManagementServerDlg_PageDesc = The Root Management Server is the first management server installed in a management group unless modified otherwise.
Property(S): RootManagementServerDlg_Note = Note: To connect to the Root Management Server you must be a member of the Operations Manager Administrators user role.
Property(S): RootManagementServerErrDlg_Desc1 = Unable to verify the Server.
Property(S): RootManagementServerErrDlg_Desc2 = We were unable to connect to the given server. Please check the server name, make sure the user running setup is MOM Administrator and try again.
Property(S): RMS_Connect_Wait_Text = Setup may take a moment to conenct to the Root Management Server. Please wait...
Property(S): CustomSetupTipsDlg_Title = Custom Setup Tips
Property(S): CustomSetupTipsDlg_Desc = Custom setup allows you to select which components to install.
Property(S): CustomSetupTipsDlg_Menu = The icon next to the component name indicates the install state of the component. Click the icon to drop down the install state menu for each component.
Property(S): CustomSetupTipsDlg_FirstInstall = Will be installed on first use. (Available only if the component supports this option.)
Property(S): CustomSetupTipsDlg_NetworkInstall = Will be installed to run from the network. (Available only if the component supports this option.)
Property(S): CustomSetupTipsDlg_InstallState = This install state means the component...
Property(S): CustomSetupTipsDlg_DontInstall = Will not be installed.
Property(S): CustomSetupTipsDlg_Partial = Will have some subcomponents installed to the local hard drive.
Property(S): CustomSetupTipsDlg_Install = Will be completely installed to the local hard drive.
Property(S): CustomSetupDlg_Title = Custom Setup
Property(S): CustomSetupDlg_Desc = Select the components that you want to install.
Property(S): CustomSetupDlg_FeatureGroup = Component description
Property(S): CustomSetupDlg_Location = <selected component path>
Property(S): CustomSetupDlg_Install = Location:
Property(S): CustomSetupDlg_ItemDescription = Multiline description of the currently selected item
Property(S): CustomSetupDlg_Size = Component size
Property(S): CustomSetupDlg_Text = Click an icon in the list below to change how that component will be installed.
Property(S): DatabaseOptionsErrDlg_Title1 = Database Size Error
Property(S): DatabaseOptionsErrDlg_Title2 = Out of disk space
Property(S): DatabaseOptionsErrDlg_Title3 = Database or Database Files Already Exists
Property(S): DatabaseOptionsErrDlg_Title4 = Database name error
Property(S): DatabaseOptionsErrDlg_Text11 = The Operations Manager 2007 database requires a minimum of 500MB size. To continue setup click Back, change the database size to be greater or equal to 500MB.
Property(S): DatabaseOptionsErrDlg_Text12 = Setup found that the selected database file locations do not contain sufficent disk space. To continue setup, go back and either choose a different drive or reduce the database size.
Property(S): DatabaseOptionsErrDlg_Text131 = Setup has found that either the database server you specified contains a MOM database or that the database file location you specified contains the [Database Name].mdf or [Database Name].ldf database files.
Property(S): DatabaseOptionsErrDlg_Text132 = To continue setup, either remove the existing database or database files, or click Back to select a different database instance or database file location.
Property(S): DatabaseOptionsErrDlg_Text14 = The database name can contain only alphabets, numbers, '-', '_' characters, should start with alphabet and cannot exceed 100 characters. To continue setup click Back, change the database name.
Property(S): DatabaseOptionsDlg_Title = Database and Log File Options
Property(S): DatabaseOptionsDlg_Desc = Enter the size for the database and the location for the database files. To change database file locations, click Advanced.
Property(S): DatabaseOptionsDlg_ReferDocs = For more information about determining the disk space required, refer to the product documentation.
Property(S): DatabaseOptionsDlg_Size = D&atabase size:
Property(S): DatabaseOptionsDlg_DBName = Database Name:
Property(S): DatabaseOptionsDlg_MB = MB
Property(S): DatabaseOptionsDlg_DataLocation = Data file location:
Property(S): DatabaseOptionsDlg_LogLocation = Log file location:
Property(S): DatabaseOptionsDlg_FilesGroup = Database files:
Property(S): AdvancedDBOptionsDlg_Title = Database Files Location
Property(S): AdvancedDBOptionsDlg_Desc = Select the location for the database and log files.
Property(S): AdvancedDBOptionsDlg_DataLoc = Database data file location:
Property(S): AdvancedDBOptionsDlg_LogLoc = Database log file location:
Property(S): RegisterUserDlg_Name = &User Name:
Property(S): RegisterUserDlg_Company = &Organization:
Property(S): RegisterUserDlg_CDKey = Enter your 25 digit CD &Key
Property(S): RegisterUserDlg_FindPID = The CD Key is on the back of the CD case.
Property(S): RegisterUserDlg_Title = Product Registration
Property(S): RegisterUserDlg_Desc = Specify your name, organization and the CD key.
Property(S): PIDErrorDlg_Desc1 = You have not entered a valid product key.
Property(S): PIDErrorDlg_Desc2 = Please check the number located on your Certificate of Authenticity or the yellow sticker on the back of the CD case.
Property(S): MUOptInDlg_Title = Microsoft Update
Property(S): MUOptInDlg_Desc = Use Microsoft Update to help keep your computer secure and up to date
Property(S): MUOptInDlg_Help = Microsoft Update offers security and important updates for Windows and other Microsoft Products including this product. Updates are delivered using your Automatic Updates setting, or you can visit the Microsoft Update website.
Property(S): MuOptinDlg_Type0 = &Use Microsoft Update when I check for updates (recommended)
Property(S): MuOptinDlg_Type1 = &I don't want to use Microsoft Update
Property(S): MuOptinDlg_FAQURL = See the Microsoft Update FAQ at http://update.microsoft.com/microsoftupdate/v6/about.aspx?ln=en
Property(S): MuOptinDlg_PrivacyURL = Read our Privacy statement online at http://update.microsoft.com/microsoftupdate/v6/privacy.aspx?ln=en
Property(S): NetFrameworkNotInstalled = The .NET Framework 2.0 is required to install this application.
Property(S): SQLServerNotFoundDlg_Title = Microsoft SQL Server 2005 Service Pack 1 or higher not found
Property(S): SQLServerNotFoundDlg_Desc = The Operations Manager 2007 database component requires Microsoft SQL Server 2005 Service Pack 1 or later. The selected instanace does not have the correct version. To continue setup, go back and choose custom setup and unselect the database component or select a different instance or upgrade the selected instance to the correct version.
Property(S): SQLServicesErrDlg_Title = Setup failed to start Microsoft SQL Server services
Property(S): SQLServicesErrDlg_Desc = The Operations Manager 2007 setup failed to start the Microsoft SQL server services. To continue setup, go back and choose a different instance or start the SQL Server services for the selected instance.
Property(S): SQLServerInstanceDlg_Note = Note: Setup will automatically start the Microsoft SQL Server service if it is not running.
Property(S): SQLServerInstanceDlg_SQLServer = SQL &Server database instance
Property(S): UserIsNotSysAdminDlg_Title = Could not verify if current user is in sysadmin Role.
Property(S): UserIsNotSysAdminDlg_ReportingDBDesc = The user running setup is not in sysadmin role in the Reporting database.
Property(S): UserIsNotSysAdminDlg_MOMDBDesc = The user running setup is not in sysadmin role in the Operations Manager database or we are unable to connect to Operations Manager database, please verify if you can connect to Operations Mangaer database from this computer.
Property(S): MOMHSPortDesc = Operations Manager Health Service.
Property(S): AgentSummaryText = {\rtf1 {\fonttbl{\f0\fmodern\fcharset0\fprq2{\*\panose 02020603050405020304}Tahoma;}} \fs16Installation Settings:\n \par1\par1 Install Directory\tab\tab\tab: %s\par1 \b0Management Group Name\tab\tab: %s \par1 Management Server DNS Name\tab: %s\par1 \b0Management Server Secure Port\tab: %s
Property(S): Data_Warehouse_Action_Account = Data Warehouse Action Account
Property(S): Data_Warehouse_Configuration_Synchronization_Reader_Account = Data Warehouse Configuration Synchronization Reader Account
Property(S): Data_Warehouse_Report_Deployment_Account = Data Warehouse Report Deployment Account
Property(S): UserExit_TextLine = The wizard was interrupted before Operations Manager 2007 could be installed.
Property(S): FatalError_TextLine = The setup wizard was interrupted before Operations Manager 2007 could be installed.
Property(S): MaintenanceDlg_Title = Operations Manager 2007 Maintenance
Property(S): MaintenanceWelcomeDlg_Text1 = The setup wizard will allow you to modify, repair, or remove Operations Manager 2007. To continue, click Next.
Property(S): ProgressDlg_Title1 = Installing Operations Manager 2007
Property(S): ProgressDlg_Title2 = Uninstalling Operations Manager 2007
Property(S): ProgressDlg_Text1 = Please wait while the wizard installs Operations Manager 2007. This may take several minutes.
Property(S): ProgressDlg_Text2 = Please wait while the setup wizard uninstalls Operations Manager 2007. This may take several minutes.
Property(S): ReadyToInstallDlg_Text1 = To install Operations Manager 2007, click Install.
Property(S): ReadyToInstallDlg_Text2 = To review or change any of your installation settings, click Back. To exit the wizard without installing Operations Manager 2007, click Cancel.
Property(S): ReadyToRemoveDlg_Text1 = To remove Operations Manager 2007, click Remove.
Property(S): ReadyToRemoveDlg_Text2 = To change your maintenance option, click Back. To exit the wizard without removing Operations Manager 2007, click Cancel.
Property(S): ReadyToRemoveDlg_Title = Remove Operations Manager 2007
Property(S): ReadyToRemoveDlg_Desc = You have chosen to remove Operations Manager 2007 from your computer.
Property(S): WelcomeDlg_Desc = The wizard will install Operations Manager 2007 on your computer. To continue, close all other programs and click Next.
Property(S): BrowseFolderDlg_Desc = Browse to the folder you want to install Reporting in.
Property(S): ExitDialog_DlgDesc1 = The wizard has successfully installed Operations Manager 2007. To close this wizard, click Finish.
Property(S): DirectorySelection_Path = Install Operations Manager 2007 in:
Property(S): WelcomeDlg_Title = Welcome to Operations Manager 2007 Reporting Setup
Property(S): Exit_Title = Completing the Operations Manager Reporting Components Setup Wizard
Property(S): MaintenanceDlg_Desc = Modify, repair, or remove the program.
Property(S): DialogWizardTitle = Operations Manager 2007 Reporting Setup
Property(S): DialogWizardTitleShort = Operations Manager 2007 Reporting Setup
Property(S): SetupTypeDlg_Text = Select a setup type.
Property(S): SetupTypeDlg_Custom = Choose which program components you want installed and where they will be installed. Use this option for installing different Reporting components on different computers.
Property(S): UnableToGetUserNameFromManagementServerActionAccountErrorDlg_Text1 = Setup was unable to retreive the Management Server Action Account.
Property(S): UnableToGetUserNameFromManagementServerActionAccountErrorDlg_Text2 = Please specify an Action Account to continue.
Property(S): UpgradeWelcomeDlg_Title = Welcome to the Operations Manager 2007 Reporting Setup Upgrade Wizard
Property(S): UpgradeVerification_Text = Upgrade Operations Manager Reporting
Property(S): Upgrade_Welcome_Text1 = Welcome to the Operations Manager 2007 upgrade wizard.
Property(S): Upgrade_Welcome_Text2 = The installation wizard will upgrade Operations Manager 2007 on your computer. To continue, close all other programs and click Next.
Property(S): UpgradeDirectorySelectionDlg_Title = Upgrade Microsoft Operations Manager
Property(S): UpgradeDirectorySelectionDlg_Text = Click Next to install to this folder, or click Change to install to a different folder.
Property(S): UpgradeDirectorySelectionDlg_Note1 = Select this option to upgrade your Ops Manager Reporting installation. Setup will remove previous versions, and install the new version based on your current configuration.
Property(S): DatabaseUpgradeWarning_Clustered = Your datawarehouse database will be upgraded when you upgrade Reporting even if your datawarehouse is on diffrerent computer, it is highly recommended that you back it up prior to starting the upgrade.
Property(S): SQLServerInstanceDlg_Title = SQL Server Database Instance
Property(S): SQLServerInstanceDlg_Desc = Select the name of the local SQL database instance that you want to host the Data warehouse database.
Property(S): CancelSetupDlg_Text = Are you sure you want to cancel the Operations Manager 2007 Reporting installation?
Property(S): CancelSetupDlg_UpgradeText = Cancelling the upgrade will render the product unstable. If the DB is installed the data stored in it could become corrupted. Are you sure you want to cancel the Operations Manager 2007 upgrade?
Property(S): ResumeDlg_ResumeText = The setup wizard will complete the suspended installation of Operations Manager 2007 on your computer. To continue, click Next.
Property(S): ResumeDlg_PreselectedText = The setup wizard will complete the installation of Operations Manager 2007 on your computer. To continue, click Next.
Property(S): ResumeDlg_Text1 = Resuming the setup wizard for Operations Manager 2007
Property(S): InitDlg_Text1 = Welcome to the Operations Manager 2007 Server Setup Wizard
Property(S): ExitDialog_DlgDesc2 = The setup wizard has successfully uninstalled Operations Manager 2007. Click Finish to exit the wizard.
Property(S): ExitDialog_DlgDesc3 = To return SQL Reporting Services to a working state, run ResetSRS.exe tool located in Support Tools directory.
Property(S): DatabaseUpgradeWarning_Text1 = It is recommended that you backup your MOM database before you upgrade to Operations Manager 2007.
Property(S): DatabaseUpgradeWarning_Text2 = Click Help to learn how to backup the MOM database. Click Next to proceed with the upgrade.
Property(S): DatabaseUpgradeWarning_Text3 = During the upgrade process the database will not be available to the DCAMs. Data will queue up on the DCAMs until the database is made available again after the upgrade is complete.
Property(S): DatabaseUpgradeWarningTitle = Database Upgrade Warning
Property(S): DatabaseUpgradeWarning_NonClustered = Your datawarehouse database will be upgraded when you upgrade Reporting even if your datawarehouse is on diffrerent computer, it is highly recommended that you back it up prior to starting the upgrade.
Property(S): SetupTypeDlg_Title = Installation Options
Property(S): SetupTypeDlg_Desc = Choose the setup type that is best for your organization.
Property(S): SetupTypeDlg_Typical = Installs the Database, Management Server and both consoles on this computer. Recommended for basic installations.
Property(S): ProgressDlg_lbStatus = Status:
Property(S): InitDlg_Text2 = Please wait while the setup wizard prepares to guide you through the setup.
Property(S): UserExit_FinishText1 = Your computer has not been modified. To install this program later, run the wizard again. To close this wizard, click Finish.
Property(S): UserExit_RestContText1 = You can either keep any existing installed elements on your system to continue this installation at a later time or you can restore your system to its original state prior to the installation.
Property(S): SetupErrorDlg_Error = <error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here>
Property(S): DWWriteAccountDlg_Title = Data Warehouse Write Account
Property(S): DWWriteAccountDlg_Text1 = The account provided will be assigned write permissions on the data warehouse and read permissions on the Operations database.
Property(S): DWWriteAccountDlg_UseLS = &Management Server Action Account
Property(S): DWWriteAccountDlg_UseDomainAccount = Do&main Account
Property(S): DataReaderAccountDlg_Title = Data Reader Account
Property(S): DataReaderAccountDlg_Text1 = The Data Reader Account will be used to define what user SQL Reporting Services uses to execute queries against the Operations Manager reporting data warehouse. This account is also used for the SQL Reporting Services IIS Application Pool account to connect to the Principal Management Server.
Property(S): DataReaderAccountDlg_Text2 = Setup will add this account to the Report Admininstator User Profile.
Property(S): SRSServerVerificationErrorDlg_Title = SRS Server Validation Error
Property(S): SRSServerVerificationErrorDlg_Text1 = Setup was unable to validate SQL Reporting Services.
Property(S): SRSServerVerificationErrorDlg_Text3 = Please use the Reporting Services Configuration tool which is installed with SQL Server to validate your SQL Reporting Services Configuration.
Property(S): OperationalDataReportsDlg_Title = Operational Data Reports
Property(S): OperationalDataReportsDlg_Yes = &Yes, send operational data reports to Microsoft (recommeded)
Property(S): OperationalDataReportsDlg_No = &No, don't send operational data reports to Microsoft
Property(S): OperationalDataReportsDlg_Text1 = Do you want to send operational data reports to Microsoft?
Property(S): OperationalDataReportsDlg_Text2 = Operational data reporting runs a report on the data warehouse to collect a summary of how the product is being used in this Management Group. Microsoft uses these reports to improve the quality of its Management Packs and products in general. These reports may sometimes contain personal information but Microsoft will not use this information to try and identify or contact you. Operations Manager Reporting must be installed in order to use this feature.
Property(S): OperationalDataReportsDlg_ViewSampleReport = Click the View Report button to view a sample report
Property(S): OperationalDataReportsDlg_ViewReportButton = &View Report
Property(S): DWServerAndDBNameDlg_Title = Connect to the Operations Manager Data Warehouse
Property(S): DWServerAndDBNameDlg_Text1 = Specify the name of the SQL Server database instance that hosts the Operations Manager data warehouse.
Property(S): DWServerAndDBNameDlg_DBInstance = &SQL Server database instance
Property(S): DWServerAndDBNameDlg_DBInstance_Example = (SQL Server\SQL Instance)
Property(S): DWServerAndDBNameDlg_DBName = &SQL database name
Property(S): DWServerDlg_DBPort = SQL Server &Port
Property(S): DWServerAndDBServerErrDlg_Title1 = DW Database Server Name cannot be Blank
Property(S): DWServerAndDBServerErrDlg_Title2 = Setup cannot locate the DW database.
Property(S): DWServerAndDBServerErrDlg_Title3 = Invalid Microsoft Operations Manager DW Database Version
Property(S): DWServerAndDBServerErrDlg_Desc11 = Missing DW database server name.
Property(S): DWServerAndDBServerErrDlg_Desc12 = To continue setup, go back and provide the database server computer name which hosts the Microsoft Operations Manager DW database.
Property(S): DWServerAndDBServerErrDlg_Desc21 = Setup could not locate the DW database on the specified server.
Property(S): DWServerAndDBServerErrDlg_Desc22 = To change the DW database server or SQL Server port information, click Back.
Property(S): DWServerAndDBServerErrDlg_Desc23 = Verify that Microsoft SQL Server is running and that the DW database is installed on the specified server, and that you have access to the DW database
Property(S): DWServerAndDBServerErrDlg_Desc31 = Setup found that the Microsoft Operations Manager database version on the specified database server is not same as the current product version.
Property(S): DWServerAndDBServerErrDlg_Desc32 = To continue setup, go back and either change the database server name or upgrade the SC database on the specified server to the current version.
Property(S): OperationalDataReportsSampleDlg_Title = Operational Data Reports Sample
Property(S): SRSDlg_Title = SQL Server Reporting Services Instance
Property(S): SRSDlg_Desc = Select the SQL instance for Reporting Services
Property(S): SRSDlg_SRS = Enter the SQL Server Reporting Services &Server:
Property(S): SRSDlg_Desc2 = Warning: The Installation of System Center Operations Manager 2007 will integrate the security of the chosen SQL Reporting Services Server Instance with OM 2007 role-based security. Any reports previously installed on this Instance may become inaccessible.
Property(S): SRSHttpBindingsDlg_Title = SQL Server Reporting Services Server
Property(S): SRSHttpBindingsDlg_Desc = Select the SQL Reporting Services Website
Property(S): SRSHttpBindingsDlg_BindingTitle = Select the &Website address you wish to use:
Property(S): SRSHttpBindingsDlg_ServerName = SQL Server Reporting Services Server:
Property(S): SRSHttpBindingsDlg_ReportServerVDir = Report Server Virtual Directory (e.g. ReportServer)
Property(S): SRSHttpBindingsDlg_ReportManagerVDir = ReportManager Virtual Directory (e.g. Reports)
Property(S): ClusterWarningCheck_Caption = &Passive node of a Windows Server Cluster
Property(S): UpgradeMOMXDlg_Text = Click Next to upgrade.
Property(S): SecureCustomProperties = ACTIONSPASSWORD;DATAREADER_PASSWORD;DBWRITEACTIONSPASSWORD;DOTNET20INSTALLED;MOM_DB_SERVER;MOMREPORTINGDBNAME_OLD;REPORTING_NEWER_PRODUCT_FOUND;REPORTING_PRODUCT_FOUND;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650;SQL_PORT
Property(S): MsiHiddenProperties = _CreateAndAddRunAsAccountsCA;_ManagementGroupConnect;_ManagementGroupDisconnect;_Rollback_ManagementGroupConnect;_Set_CreateAndAddRunAsAccountsCA.9B663534_CD9B_41CC_9D93_4E84D3C5E165;_Set_ManagementGroupConnect.9B663534_CD9B_41CC_9D93_4E84D3C5E165;_Set_ManagementGroupDisconnect.9B663534_CD9B_41CC_9D93_4E84D3C5E165;_Set_Rollback_ManagementGroupConnect.9B663534_CD9B_41CC_9D93_4E84D3C5E165;_Set_SetSRSAccount.9B663534_CD9B_41CC_9D93_4E84D3C5E165;_Set_SetSRSSecurityCA.9B663534_CD9B_41CC_9D93_4E84D3C5E165;_SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;_SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;_SetSRSAccount;_SetSRSSecurityCA;_StoreActionsAccount.80B659D9_F758_4E7D_B4FA_E53FC737DCC9;ACTIONSPASSWORD;DATAREADER_PASSWORD;DBWRITEACTIONSPASSWORD;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650
Property(S): DB_DATA_DIR = F:\SCE 2007\MSSQL.4\MSSQL\DATA\
Property(S): DB_LOG_DIR = F:\SCE 2007\MSSQL.4\MSSQL\DATA\
Property(S): VersionNT = 502
Property(S): SQLSVR_INSTANCE = WSMOSS\SCE
Property(S): INSTALLDIR = C:\Program Files\System Center Essentials 2007\
Property(S): TempDataDir = C:\Program Files\System Center Essentials 2007\Reporting\MSSQL\data\
Property(S): TempLogDir = C:\Program Files\System Center Essentials 2007\Reporting\MSSQL\data\
Property(S): USERNAME = WorldSynergy
Property(S): COMPANYNAME = World Synergy
Property(S): DBWRITEACTIONSUSER = administrator
Property(S): DBWRITEACTIONSPASSWORD = **********
Property(S): DBWRITEACTIONSDOMAIN = WS
Property(S): DATAREADER_USER = administrator
Property(S): DATAREADER_PASSWORD = **********
Property(S): DATAREADER_DOMAIN = WS
Property(S): SRS_SERVER = WSMOSS\SCE
Property(S): REPORT_SERVER_FULL_HTTP_PATH = http://WSMOSS:80/ReportServer$SCE
Property(S): REPORT_SERVER_VDIR = ReportServer$SCE
Property(S): REPORT_MANAGER_VDIR = Reports$SCE
Property(S): MGSERVER = WSMOSS
Property(S): MOM_INSTALL_DIR = C:\Program Files\System Center Essentials 2007\
Property(S): DOTNET20INSTALLED = #1
Property(S): REPORTINGDIR = C:\Program Files\System Center Essentials 2007\Reporting\
Property(S): SQLROOTDATADIR = C:\Program Files\System Center Essentials 2007\Reporting\MSSQL\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): TARGETDIR = F:\
Property(S): Privileged = 1
Property(S): DatabaseModuleDir.128A4B6A_C876_40B8_83B5_2793414E2138 = C:\Program Files\System Center Essentials 2007\Reporting\
Property(S): DATABASE_DIR = C:\Program Files\System Center Essentials 2007\Reporting\Database\
Property(S): REPORTSFOLDER.9B663534_CD9B_41CC_9D93_4E84D3C5E165 = C:\Program Files\System Center Essentials 2007\Reporting\Reports\
Property(S): DWReportLibrary.9B663534_CD9B_41CC_9D93_4E84D3C5E165 = C:\Program Files\System Center Essentials 2007\Reporting\Reports\Microsoft.SystemCenter.DataWarehouse.Report.Library\
Property(S): SDK_DIR.9B663534_CD9B_41CC_9D93_4E84D3C5E165 = C:\Program Files\System Center Essentials 2007\Reporting\
Property(S): SRSFILEFOLDER = C:\Program Files\System Center Essentials 2007\Microsoft SQL Server\MSSQL.5\Reporting Services\ReportServer\bin\
Property(S): REPORTINGFOLDER = /
Property(S): MYREPORTSFOLDER = My Reports
Property(S): MOM_SRS_ASSEMBLY_NAME.9B663534_CD9B_41CC_9D93_4E84D3C5E165 = Microsoft Operations Manager Reporting Code Assembly
Property(S): MOM_SRS_ASSEMBLY_DESC.9B663534_CD9B_41CC_9D93_4E84D3C5E165 = Grants the MOM Reporting Code assembly full trust permission.
Property(S): CHARTING_ASSEMBLY_NAME.9B663534_CD9B_41CC_9D93_4E84D3C5E165 = EnterpriseChartControl
Property(S): CHARTING_ASSEMBLY_DESC.9B663534_CD9B_41CC_9D93_4E84D3C5E165 = This codegroup grants FullTrust to EnterpriseChartControl assemblies.
Property(S): NetFxVersion = v2.0.50727
Property(S): TOOLS.68918168_3885_4F75_BBF8_0CC84213F8D1 = C:\Program Files\System Center Essentials 2007\Tools\
Property(S): PackageCode = {7164D0F8-3AEA-4994-ABE0-560481D11BA6}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): SCEREPORTING = True
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): SRSOEMFILES = E:\SCERetailRTM\Setup\ReportingImages
Property(S): ADDLOCAL = ALL
Property(S): DATA_DIR = f:\SCE 2007\MSSQL.4\MSSQL\DATA\
Property(S): LOG_DIR = f:\SCE 2007\MSSQL.4\MSSQL\DATA\
Property(S): PIDKEY = fw6bkg8mgxky6hftvddjkvptq
Property(S): CURRENTDIRECTORY = C:\DOCUME~1\ADMINI~1.WS\LOCALS~1\Temp
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 4300
Property(S): CURRENTMEDIAVOLUMELABEL = MAPSOCWnSvrEN
Property(S): VersionDatabase = 200
Property(S): VersionMsi = 3.01
Property(S): WindowsBuild = 3790
Property(S): ServicePackLevel = 2
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): SystemFolder = C:\WINDOWS\system32\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\DOCUME~1\ADMINI~1.WS\LOCALS~1\Temp\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and Settings\administrator.WS\Application Data\
Property(S): FavoritesFolder = C:\Documents and Settings\administrator.WS\Favorites\
Property(S): NetHoodFolder = C:\Documents and Settings\administrator.WS\NetHood\
Property(S): PersonalFolder = \\SBS\Users\administrator\My Documents\
Property(S): PrintHoodFolder = C:\Documents and Settings\administrator.WS\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\administrator.WS\Recent\
Property(S): SendToFolder = C:\Documents and Settings\administrator.WS\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and Settings\administrator.WS\Local Settings\Application Data\
Property(S): MyPicturesFolder = \\SBS\Users\administrator\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 15
Property(S): PhysicalMemory = 4094
Property(S): VirtualMemory = 4209
Property(S): AdminUser = 1
Property(S): LogonUser = administrator
Property(S): UserSID = S-1-5-21-3943162657-1640162975-2022637984-500
Property(S): UserLanguageID = 1033
Property(S): ComputerName = WSMOSS
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 792
Property(S): ScreenY = 615
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 16
Property(S): TTCSupport = 1
Property(S): Time = 11:18:49
Property(S): Date = 10/16/2007
Property(S): MsiNetAssemblySupport = 2.0.50727.42
Property(S): MsiWin32AssemblySupport = 5.2.3790.3959
Property(S): RedirectedDllSupport = 2
Property(S): DATABASE = C:\WINDOWS\Installer\76e64.msi
Property(S): OriginalDatabase = E:\SCERetailRTM\Setup\i386\Reporting2007.msi
Property(S): UILevel = 2
Property(S): Preselected = 1
Property(S): ACTION = INSTALL
Property(S): ROOTDRIVE = F:\
Property(S): CostingComplete = 0
Property(S): SRS_INSTANCE_REGISTRY_LOCATION = MSSQL.5
Property(S): SRS_SQL_INSTANCE = WSMOSS\SCE
Property(S): SRS_INSTANCE_NAME = SCE
Property(S): SRS_SERVICE_NAME = ReportServer$SCE
Property(S): SRS_SQL_DATABASENAME = ReportServer$SCE
Property(S): SRSREPORTSERVERFOLDER = C:\Program Files\System Center Essentials 2007\Microsoft SQL Server\MSSQL.5\Reporting Services\ReportServer\
Property(S): SRSCONFIGFILE = C:\Program Files\System Center Essentials 2007\Microsoft SQL Server\MSSQL.5\Reporting Services\ReportServer\rssrvpolicy.config
Property(S): MANAGEMENT_GROUP = WSMOSS_MG
Property(S): resolvedMG = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): REPORT_SERVER_FULL_HTTP_PATH_VALID = 1
Property(S): MGSQLSERVER = WSMOSS\SCE
Property(S): MGDATABASE = OperationsManager
Property(S): UnableToGetUserNameFromManagementServerActionAccount = SetPropertiesToManagementServerActionAndSDKAccountCA: Error: Unable to get the Management Server Action Account.
MSI (s) (00:58) [11:18:49:763]: Note: 1: 1708
MSI (s) (00:58) [11:18:49:763]: Product: System Center Operations Manager 2007 Reporting Server -- Installation operation failed.
MSI (s) (00:58) [11:18:49:763]: Cleaning up uninstalled install packages, if any exist
MSI (s) (00:58) [11:18:49:763]: MainEngineThread is returning 1603
MSI (s) (00:1C) [11:18:49:872]: Destroying RemoteAPI object.
MSI (s) (00:60) [11:18:49:872]: Custom Action Manager thread ending.
=== Logging stopped: 10/16/2007 11:18:49 ===
MSI (c) (CC:7C) [11:18:49:872]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (CC:7C) [11:18:49:872]: MainEngineThread is returning 1603
=== Verbose logging stopped: 10/16/2007 11:18:49 ===
Reply:
Are you using the hotfix rollup that addresses this issue?
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2207586&SiteID=17
------------------------------------
Reply:
Hi,
According to your log, I suppose it is a SCOM log. Aware of the differences between SCE and SCOM, I would like to double confirm with you.
If it is question about System Center Operations Manager 2007, please use the Microsoft public newsgroups for SCOM (microsoft.public.opsmgr.setup) which would be the most relevant newsgroup for your question.
microsoft.public.opsmgr.setup
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.opsmgr.setup
Also, I found a KB article related to this issue, for your reference:
You cannot install the System Center Operations Manager 2007 Reporting feature in a disjointed namespace environment
http://support.microsoft.com/?id=936481
Hope it helps.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
------------------------------------
Reply:
I have not tried the hotfix yet, I will try that today. And the version is SCE not MOM or SCOM.
------------------------------------
Reply:
Hi,
Thanks for your confirm.
Let's wait and see whether the hotfix can do helps. If there are any update, please feel free to post back here.
I will assist you and also provide you with our full support.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
------------------------------------
Reply:
Ok, I attempted the installation again after completely removing any remnants of the failed installation and using the provided hotfix, but to no avail. I am still recieving the same error as before. Any other suggestions?
------------------------------------
Reply:
Is the database on the same server?
I am sure I read somewhere that in a disjointed domain namespace the SQL server has to be on the SCE box.
just a thought.
Mark
------------------------------------
Reply:
Thanks for the though, but I am installing this on the same server. I even tried installing my own full version of SQL 2005 standard, but that didn't work so I wiped that out.
------------------------------------
Reply:
Hi,
Thanks for your update.
I would like to confirm with you about 2 important information:
1. Are you using disjoint namespace?
Disjoint namespace means you are in one of the following scenario:
a. The computer on which you try to install Essentials 2007 has a domain suffix that does not match the fully qualified domain name (FQDN) of the domain. For example, the computer has a domain suffix of department.contoso.com. However, the domain is named contoso.com.
b. The computer on which you try to install Essentials 2007 has a NetBIOS domain name that does not match the first part of the FQDN of the domain. For example, the NetBIOS domain name is CONTOSO-XYZ. However, the domain is named contoso.com instead of contoso-xyz.com.
If this is the case, have you applied the hotfix 937831 which was mentioned in Stephanie's previous reply?
2. Which version of database you are using? Had sp1 or higher version of service pack had been applied on the DB server?
Thanks.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
------------------------------------
Reply:
No, it's not a disjointed domain and I am just trying to get the SQL express that installs with SCE to work. Also, I did apply the hotfix. Same error.
------------------------------------
Reply:
------------------------------------
Reply:
Hi,
Thanks for your information.
Please notice that SCE does not support SQL express version. The default SQL version is SQL Express Advanced, you can find it under SCE install media\Setup\SQLEXPR_ADV.exe.
Let's try to configure SRS before SCE installation, following are the steps:
1. Create a new named instance, including DB and SRS component. You can use the following steps:
1) Launch SQL installation.
2) On the Installing Prerequisites page, click Next when the installation of the required components completes.
3) On the "Welcome To The Microsoft SQL Server Installation Wizard" page, click Next.
4) Select the appropriate components to install by checking the box next to the Component (choose DB and Reporting Services), and then click next.
5) Install a named instance.
6) Configure the service account information and the component startup information by selecting domain user account and then click next.
7) In next screen, configure the service account information and the component startup information by selecting windows authentication mode. Then click next.
8) Select "Install the default configuration" (Recommended).
9) At last, confirm which components will be installed and click install.
2. After installing a new instance, please use the following steps to configure SQL Server Reporting Service:
1) Open Start->Programs->Microsoft SQL Server 2005->Configuration Tools->Reporting services configuration. Choose the new instance you created and then click "Connect".
2) Follow the wizard to finish all the configurations one by one listed on the left pane.
More Information regarding SRS:
TechNet Webcast: Overview of SQL Server 2005 Reporting Services (Level 200)
http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032273491&EventCategory=5&culture=en-US&CountryCode=US
Reporting Services Configuration F1 Help
http://technet.microsoft.com/en-us/library/ms187055.aspx
Reporting Services Configuration Tool
http://technet.microsoft.com/en-us/library/ms156305.aspx
Reporting Services Configuration How-to Topics
http://msdn2.microsoft.com/en-us/library/ms157412.aspx
If you need more assistance on SRS or encounter specific problems when configuring SRS, you are welcome to post in our related SQL Server Reporting Services Forum:
SQL Server Reporting Services - TechNet Forums
http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=82&SiteID=17
3. Click Start->All Programs-> Microsoft SQL Server 2005->SQL Server Management Studio. Choose Server Type to Reporting Service, click Connect to verify whether you can connect to reporting service correctly.
4. Launch SCE installation. Especially, during the SCE installation, ensure the new instance is selected.
Hope it helps.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
------------------------------------
Reply:
Thanks. I am attempting to install SQL server 2005 Standard with SRS, however it doesn't seem to install SRS properly. I have gone through the SRS configuration utility and all items are checked green on the left side, however, when I open the SQL configuration manager, it says that there is no SRS instance. So, I reinstalled and re-ran through the configuration and set up new virtual sites and new databases, etc...but I still am recieving the same error. And of course, the SCE installation won't detect any installed SRS instance if SQL won't. So that's where I'm at now, I'm searching through the SRS forums for the answer, but it would be helpful if you knew where to look exactly. Thanks.
Matt
------------------------------------
Reply:
Hi Matt,
May I know how you install the SRS?
Based on my experience, double click the SQL install file will install another SQL instance.
Here is the detail steps to install SRS component:
1. Go to Add/Remove Programs, Select Microsoft SQL Server 2005.
2. Click Change, then select the SQL instance to include the SRS component.
3. Click "To install a new component, click here"
4. Browse to the right path of SQL install file.
5. Following the wizard to reinstall the Reporting Service Component.
6. Don't forget to apply SQL SP1 or higher Service Pack after finished for SRS component.
You may also like to check the similar thread:
SCE failure during reporting
http://forums.microsoft.com/technet/showpost.aspx?postid=1779770&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=1
Hope it helps.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
------------------------------------
Reply:
Hi Matt,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as 'Answered' as the previous steps should be helpful for many similar scenarios.
If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
In addition, we'd love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
Thanks!
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
------------------------------------
Reply:
------------------------------------
Reply:
Hi Matt,
Thanks for your information.
If you have any updates, please feel free to let us know. We will be happy to provide further assistant.
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
------------------------------------
Reply:
Hi Matt,
Since this issue was wait pending SSRS correctly configured, we will be changing the thread status to 'Comment'.
If you wish to return to this question you can go ahead and change the type back to 'Question'. Then you can edit your initial post and change the radio button at the top of the post editor window.
If the issue has been resolved, we'd love to hear your solution. By sharing your experience you can help other community members facing similar problems.
Hope you can understand.
Thanks!
-----------------------------
Sincerely,
Guozhen Wang
Microsoft Online Community Support
------------------------------------
Boot Configuration on Windows Vista Upgrade
I am getting an error that stated that I cannot upgrade my windows vista becuse it cannot change my boot configuration
Reply:
Hi MiloMex,
Thank you for your post.
First please help confirm the following three points:
1. Are you trying to upgrade the install Vista over XP?
2. At what stage does the error appear?
3. What's the exact wording of the error message?
Generally, if we upgrade the install Vista over XP, we need to install Vista in XP (not boot from the Vista DVD) and make sure the upgrade partition is NTFS. In addition, please confirm if there is only one operating system existing on the upgrade partition. If there are multiple operating systems, we cannot install Vista on the upgrade partition.
Please confirm the upgrade path in the article below and paste the contents of the boot.ini file to your post. http://www.microsoft.com/windows/products/windowsvista/buyorupgrade/upgradepaths.mspx
Save a Backup Copy of Boot.ini
===========================
1. Right-click My Computer, and then click Properties.
2. On the Advanced tab, click Settings under Startup and Recovery.
3. Under System Startup, click Edit. The file will open in Notepad ready for editing.
4. In Notepad, click File on the Menu bar, and then click Save As.
5. Right click in an empty area of the Save As dialog box, point to New in the Context menu, and then click Folder.
6. Type a name for the new folder, for example temp, and then press ENTER to create this folder.
7. Double-click this folder, and then click Save to save a backup copy of the Boot.ini file.
Then you can open the Boot.ini file and paste its contents to your post.
Best regards,
Tim Quan
Microsoft Vista Forum Support Professional
------------------------------------
Reply:
Hi MiloMex,
As this thread has been quiet for a while we will be changing the issue type to 'Comment'.
If you wish to return to this question you can go ahead and change the type back to 'Question'. Then you can edit your initial post and change the radio button at the top of the post editor window.
If the issue has been resolved, we'd love to hear your solution. By sharing your experience you can help other community members facing similar problems.
Thanks!
Best regards,
Tim Quan
Microsoft Vista Forum Support Professional
------------------------------------
Reply:
------------------------------------
Temporarily Solution
after i got tired, i found that the SPS sould be a DC (not enough member server) to let SSO service work.
i used the local SpsServer\Administrator (SharePoint=System account) for SSO authentication and i got this message:
A Single Sign-on error has occurred. Please contact an administrator. Details: Could not find domain controller for this domain
the problem with me is : the DC in my compaby is Windows Small Business and the Sharepoint Server is Windows Server 2003 Enterprise Edition.
when i get the solution to solve the problem I'll try to send the results.
by the way the buckup could be solved by two ways :
1) export the website (from SPS) as a temlate.
2) make divided backup for the website without the SSO service backup.
it's a temporarily solution untill we could at least move the website to another site.
Port TS001
Hi,
what the heck are these TS001 - TS004 ports?
one of them will be added after a client machine installs a shared printer that's on a print server.
it's only for viewable, can't delete or change. eventually, the client machine is also add this port and once that happens, i can't print.
thanks,
Installing SteadyState 2.0 in a XP Shared Computer Toolkit 1.2 domain environment. Error message
I have the XP Shared Computer Toolkit 1.2 in a domain enviroment. I am upgrading to the Windows SteadyState 2.0 on the domain.
I have created a new Group Policy and have the new user and Computer in that Group. I have added the new SCTsettings.adm to the template for that group and installed Windows SteadyState on the new computer.
I am recieving the following error message: "Cannot find script file "C:/Program Files/Windows SteadyState/bin/SCTLogoff.vbs"
I have removed SteadyState from the PC. Removed and added the 2.0 template again and I still recieve the error message.
This is being used in a public library setting and I would like to move the PC's and users to the new Group Policy one at a time.
Thanks,
Denny
Reply:
Hi Denny,
This issue can occur if Shared Computer Toolkit was not completely uninstalled before installing SteadyState. You can refer to the following thread:
Using SCTSetting.adm Timer in Group Policy
http://forums.microsoft.com/WindowsToolsandUtilities/ShowPost.aspx?PostID=1765747&SiteID=69
Best Regards,
------------------------------------
Reply:
Thanks Shawn,
I have tried those changes to no avail.
As soon as I enable the Group Policy on the Server the local PC registry entry changes back to
"%windir%\system32\WScript.EXE %SCTPath%bin\SCTLogoff.vbs"
I have removed the template from the Group Policy on the server and double checked that the new version 2.0 template is being used.
I have tried to manually enter the registry entry and as soon as I log back on to the server the registry entry is changed back.
Can both templates exist on the server and be added to different group policy objects?
I have also checked to see that the old SCTsettings template is not being inherited.
thanks,
Denny
------------------------------------
Reply:
Hi Denny,
Do you have Windows Disk Protection (WDP) enabled on the client computers? If so, you may need to configure it to "Retain all changes permanently" to save changes. Please also make sure your user profiles haven't been locked.
In addition, you can run "gpupdate /force" to updates the group policies on local computers. After that, please log off and log on to test.
Regards,
------------------------------------
Reply:
No, the Windows Disk Protection is not enabled on the client computers and I have already done the gpupdate /force command.
Thanks,
Denny
------------------------------------
Reply:
Hi Deny,
Did this issue still occur after removing SCTSettings.adm from the server? If so, please make sure Shared Computer Toolkit has been completely removed from the clients.
Please also let me know your steps to add/remove group policy template.
Steps to add SCTSettings.adm in SteadyState Handbook:
-----------------------------
1. Start Active Directory Users and Computers on a computer running Microsoft Windows Server 2003 by clicking Start, and then clicking All Programs.
2. Click Administrative Tools. In Active Directory Users and Computers, right-click the organizational unit (OU) for which you want to configure policy, and then click Properties.
3. On the Group Policy tab, select the policy you want to modify, and then click Edit.
4. Expand User Configuration, right-click the Administrative Templates folder, and then click Add/Remove Templates.
5. In the Add/Remove Templates dialog box, click Add and then browse to the location of the SCTSettings.adm template, commonly located in C:\Program Files\Windows SteadyState\ADM.
6. Browse the settings in the All Windows SteadyState Restrictions folder and note their similarity to the program and user restrictions settings in Windows SteadyState. Descriptions are given for each setting.
7. Make any restrictions changes that you want and then exit Group Policy Editor.
When removing the template, please not only delete the template, but also the group policy on the OU. You can also delete the policy from the sysvol folder of your server.
Best Regards,
------------------------------------
Import Error when Discusion subject ends whith ".aspx"
I am having problems importing .cmp files from one server with WSS 3.0 and embedded content database to a diferent server with WSS over SQL Server 2005 Std.
Export goes OK using the object model inside an ASP page on the "from" server, but when I try to do the import on the "to" server I get a security error... so I tried to make import using stsadm.
Here I get a warning about some "not especified security information" in my export file, but process continues.. after a few well exported files I get this error:
==================================================================================
Progress: Importando Carpeta /Lists/Discusion de grupo/Problemas con newItem.aspx.
FatalError: Esta operación sólo puede realizar en un archivo; "Lists/Discusion de grupo/Problemas con newItem.aspx" es una carpeta.
en Microsoft.SharePoint.Library.SPRequest.UpdateFileOrFolderProperties(String
bstrWebUrl, String bstrWebRelativeUrl, Object varProperties, Int32 fMigrationSemantics, Int32 fReGhost)
en Microsoft.SharePoint.SPFolder.UpdateOnImport()
en Microsoft.SharePoint.Deployment.FolderSerializer.SetObjectData(Object obj,
SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
en Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType,
Boolean isChildObject)
en Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type object
Type, Boolean isChildObject, DeploymentObject envelope)
en Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
en Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
en Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)
en Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
en Microsoft.SharePoint.Deployment.SPImport.Run()
...
Esta operación sólo puede realizar en un archivo; "Lists/Discusion de grupo/Problemas con newItem.aspx" es una carpeta.
==================================================================================
translating the bolded text it may sense: "this operation can only be executed with a file; "Lists/Discusion de grupo/Problemas con newItem.aspx" is a folder".
The solution was quite simple, deleting this discusion item.
But other items into this discusion list were well-exported... so I thougt the subject of the discusion could cause the problem... and I found that whenever I write a subject ended with .aspx it fails....
Custom action for SPD -- code available for download
Greetings,
I've put together a package for download that may serve as a useful template and/or starting point for creating custom actions that integrate with SharePoint Designer.
It's described in more detail here: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!275.entry
I hope the community finds this to be helpful. I welcome any and all feedback.
Regards,
HELP !! Getting BlueScreen once a day !!!
I have tried to look around and check what might be causing it, but Vista does not really give you much to go with..
Can someone help please ? I am losing so much data, it will be impossible to keep working !!!
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: 80000005
BCP2: 00000008
BCP3: 80000005
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\Mini102807-01.dmp
C:\Users\ariane\AppData\Local\Temp\WER-2380497-0.sysdata.xml
C:\Users\ariane\AppData\Local\Temp\WER98C6.tmp.version.txt
Ariane
Reply:
Hi Ariane,
Thank you for your post.
First, please help to confirm the following four points:
1. Does the whole screen become blue?
2. Does the blue screen appear when starting/shutting down the computer or using a certain program?
3. When did the issue begin to occur?
4. Have any changes been made on the computer recently, such as an installation or upgrade?
5. Are the error messages on the blue screen always the same?
Usually, blue screen issues are caused by incompatible hardware or device drivers.
Please help me collect minidump files for research.
1. Click Start, right-click Computer and click Properties.
2. Click "Advanced system settings" and click the "Settings" button under "Startup and Recovery".
3. Uncheck the box before "Automatically restart".
4. Under "Write debugging information" section, make sure the "Small Memory Dump (64KB)" option is selected.
5. Check if "%SystemRoot%\Minidump" is in the "Small Dump Directory" open box.
6. Click OK.
If the Blue Screen appears again, please let me know if any error message like "Stop: 0xXXXXXXXX, <file name>.sys" appears
Meanwhile, please go to C:\Windows\Minidump and send the memory dump files (looks like Mini052006-01.dmp) to me.
I have created a FTP site and you can upload the files to me from the following the following site:
https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=f89599c5-31c0-4116-a572-f8c199311e64
Password: T]^I[J!I-L
Note: you can copy and paste the password to avoid mistyping.
Best regards,
Tim Quan
Microsoft Vista Forum Support Professional
------------------------------------
Reply:
Tim,
File uploaded.
RE. your questions:
1. Does the whole screen become blue? hmmm, yes. the famous blue screen of death... unless you count the white characters on it ? 
2. Does the blue screen appear when starting/shutting down the computer or using a certain program?
No, random crashes - do not seem to be related to using any app in particular.
3. When did the issue begin to occur?
First time was 10/23/2007 12:35 PM
Have had one/day since, times vary... same signature and info - actually they seem identical"
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
Extra information about the problem
BCCode: 1000008e
BCP1: C0000005
BCP2: 926B653E
BCP3: 98850AB8
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1
Server information: e9236dcd-b959-4e03-9413-bd924175acdc
4. Have any changes been made on the computer recently, such as an installation or upgrade?
No upgrades - this is a new Windows Vista machine.
Installations, yes - the last thing installed was my Canon printer - but I have another identical laptop, same version of windows, where the same printer was installed and caused no problems...?
The canon driver is vista compatible (according to canon) - the printer is the IP6700D.
5. Are the error messages on the blue screen always the same?
Yes - I changed the auto-restart to get you exactly what it says - but I though the prob sig I posted above was it ??
Thanks for looking into it !
Ariane
------------------------------------
Reply:
Ariane,
Thank you for your reply and sending me the minidump file.
I have researched the minidump file but no helpful information is included in it.
As this issue began from 10/23/2007, I suggest we try to restore the system before the issue occurred if the System Restore feature is enabled on your Vista.
Start->All Programs->Accessories->System Tools->System Restore.
Since blue screen issues are usually caused by incompatible hardware, you can also disable unnecessary devices such as printers, sound cards, network cards, TV cards and CD/DVD drives in Device Manager to test the issue. As blue screens do not appear frequently, this can be somewhat time-consuming to check the results but it is a method that can help us find the cause of the issue.
Best regards,
Tim Quan
Microsoft Vista Forum Support Professional
------------------------------------
Reply:
Hi Ariane,
As this thread has been quiet for a while we will be changing the issue type to 'Comment'.
If you wish to return to this question you can go ahead and change the type back to 'Question'. Then you can edit your initial post and change the radio button at the top of the post editor window.
If the issue has been resolved, we'd love to hear your solution. By sharing your experience you can help other community members facing similar problems.
Thanks!
Best regards,
Tim Quan
Microsoft Vista Forum Support Professional
------------------------------------
Reply:
Tim,
I am also having the same problem and was wondering if I can receive some help. I just purchased this computer brand new a week ago and when I was saving a PDF file from my Internet e-mail account (Comcast) to an external hard drive that is connected to my computer, I received a blue screen and the related information is as follows:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: 8000000D
BCP2: 00000001
BCP3: 81CE827C
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\Mini113007-01.dmp
C:\Users\Saeid\AppData\Local\Temp\WER-89279-0.sysdata.xml
C:\Users\Saeid\AppData\Local\Temp\WER22DB.tmp.version.txt
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
This problem has only occured the one time and I was going to refund the computer altogether, but realized that this is probably a Vista issue. Therefore, getting a new computer with the same OS will not be helpful. Can you help me?
AmirSaeid
------------------------------------
Reply:
Hi AmirSaeid
Thank you for the post.
Please understand that to troubleshoot the blue screen issues, we usually need to perform debugging. Unfortunately, debugging is now beyond what we can do in the forum. If you would like to perform debugging, please contact Microsoft Customer Support Service (CSS).
To obtain the phone numbers for specific technology request, please refer to the website listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
I hope the problem will be resolved soon. Thank you for your time and cooperation!
Best regards,
Tim Quan
Microsoft Online Community Support
------------------------------------
How to use upgrade definition file in WSS 3.0?
Adding Date and Time
Nive, we've got date and time as pure new data types, which is great. I have some further comments, which I would like to get some comments on.
You cannot directly add a date and a time. I find this would be nice, and I would expect the result to be of the datetime datatype.
You can compare the date and datetime datatype, but what seems to happen is an explicit typecast of the date column to datetime, and the comparison will almost always fail. Would it not be better if the datetime column were narrowed to date? And similar for time. I find it pretty obvious that if someone want to compare a date and datetime column, they're actually interrested in comparing only the date part.
no sound
I don't have any sound so what should i do
How to setup test users for Exchange Server 2007
Here is a Powershell script for creating 100 test users. It creates the domain user and mailbox at the sametime.
$Temp = ConvertTo-SecureString "myPassWord" -asPlainText -force 1..100 | ForEach { New-Mailbox -Name "User$_" -UserPrincipalName "User$_@contoso.com" -database "Mailbox Database" -Password $temp -OrganizationalUnit Users }
Outlook 2003 not working with new Exchange Server 2007 - Error "Unable to open your default e-mail folders".
I'm having trouble creating ANY profile under ANY login account in Outlook 2003 for one client now that we're using Exchange 2007 on a new server! I've tried the many approaches already posted but this problem persists. The details of the error message are " This error can occur if you attempt to run Outlook from a Terminal Server session when the OST file is in use by the console session. To access this instance of Outlook, exit the current Terminal Server session and start a new session by using the following RUN command: mstsc.exe /console". It appears something has a "Hold" on the OST file and the only thing I haven't tried is deleting or renaming it. I will try that next but wanted to post this for some additional help. Our administrator also installed Office Communicator on the server but no one else is having this problem. Any help would be appreiciated!
Thanks!!
I was unsuccessful at creating a profile using "Cached Exchange Mode" so I disabled it to get the users Outlook going. This is not our normal/correct way of using Outlook with Exchange Server but it will do for now. I've noticed some users running this mode before but was able to enable it without problems. Anyone have any ideas?
Thanks!
Reply:
This looks to be a profile issue with that user. i would have that user log off, delete the profile from the terminalserver, once you save any data that needs to be saved, then log back in to the server as that user and try it again. By you stating that others arent effected, it makes me think it is a terminal server profile issue.
Also, when you installed the Outlook client, did you put the server in /install mode? then back to user mode?
------------------------------------
Reply:
We may try blowing out this particular Exchange account after backing up her mailbox of course but we currently have bigger fish to fry!! Thanks for the Information.
------------------------------------
Reply:
------------------------------------
Reply:
------------------------------------
Vista Will not boot / shut off
I just bought a computer containing Vista 32 bit Ultimate and I ran the update and upon the end of the update the screen turned black and monitor stopped recieving input. I cannot restart/shut off from there so I turned it off from the back and when I attempt to turn it on my screen dosnt recieve any input and computer just seems to idle there doing nothing.
*update* I did some research and found out the people who built my computer put in a set of Non-Compatiable DDR2 into the system when I removed it then it seems to reboot n run fine.
How to act (on behalf of || as) other users - Delegation and Impersonation (Exchange Web Services)
In Exchange Server 2007 Web services, there are 2 ways to act on another users account.
Delegation -- To act on behalf of another user, the Exchange Web Services (EWS) provides a means to do this.
- To start, first create a FindFolder or FindItem request. In the DistinguishedFolderId element, create a child Mailbox element that identifies the account the has granted delegate access to the caller of the EWS operation.
- All the item/folder identifiers returned in the response will be identifiers in the delegators mailbox. Use these identifiers in future requests.
- Make sure that requests use the delegator's folder identifiers. If a request is made that implies the use the caller's mailbox, then an error will be thrown.
Here is an example of delegation:
<soap:Body>
<FindItem xmlns="http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"
Traversal="Shallow">
<ItemShape>
<t:BaseShape>IdOnly</t:BaseShape>
</ItemShape>
<ParentFolderIds>
<t:DistinguishedFolderId Id="inbox">
<t:Mailbox>
<t:EmailAddress>User2@example.com</t:EmailAddress>
</t:Mailbox>
</t:DistinguishedFolderId>
</ParentFolderIds>
</FindItem>
</soap:Body>
Exchange Impersonation (Server to server auth) -- An account or user impersonates a user.
- In the SOAP Header, set either the UPN, SID, or primary SMTP address of the user to impersonate in the ConnectingSID element.
- Make the call as if it were a normal request. The request will be made as if the caller was the impersonated user. The CAS logs the operation as if the impesonated user made the call.
Here is an example of impersonation:
<soap:Header>
<t:ExchangeImpersonation>
<t:ConnectingSID>
<t:PrincipalName>User2@example.com</t:PrincipalName>
</t:ConnectingSID>
</t:ExchangeImpersonation>
</soap:Header>
<soap:Body>
<FindItem xmlns="http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"
Traversal="Shallow">
<ItemShape>
<t:BaseShape>IdOnly</t:BaseShape>
</ItemShape>
<ParentFolderIds>
<t:DistinguishedFolderId Id="inbox"/>
</ParentFolderIds>
</FindItem>
</soap:Body>
Reply:
Thanks Michael. Can you briefly discuss permissions?
In Exchange 2003 if we were to do this with DAV we would have had to set the "Receive As" and "Send As" permissions for the store (or after the recent hot fix, on the individual users in AD.) Is this still the case for delegation? I have yet to succeed with this. I see an "Allow Impersonation to Exchange Info" permission in the new AD user schema. Is this the key?
And for impersonation, can you discuss the underlying mechanism? Is it constrained delegation? What are the steps for giving permissions to the server to achieve this?
------------------------------------
Reply:
It turns out this information is available on Connect in the Documents section. "Exchange 2007 Partner ISV/IHV TAP Home"/"Documents"/"Web Services - Athentication and Impersonation documentation".
It looks to be pretty complete for impersonation (though it doesn't seem to have anything to help with delegation) and has pictures to help those of us who struggle to RTFM. Thanks guys.
------------------------------------
Reply:
Here is some information about setting permissions using PowerShell:
The example at the bottom shows how to set "send as" permissions. I hope this helps.
------------------------------------
Reply:
Very helpful. The key permissions for Impersonation to work are:
ms-Exch-EPI-Impersonation ("Exchange Web Services Impersonation") which needs to be set on the SERVER'S security descriptor
ms-Exch-EPI-May-Impersonate ("Allow Impersonation to Personal Exchange Information"), which needs to be granted on the MAILBOX security descriptor
------------------------------------
Reply:
Just as an aside, you can put the MayImpersonate right on:
1. The mailbox security descriptor (user object in the AD). This will give the caller access to impersonate that specific mailbox.
2. The mailbox database in the AD. This will give the caller rights to impersonate ALL mailboxes in that database. Note that in this case, you can hand pick mailboxes to deny access to if there are a couple in the database that you don't want to be impersonated. The denys will override the database wide allows.
3. A cross-forest contact in the AD. As long as the cross-forest contact has a ms-Exch-MasterAccountSid and an Exchange Legacy DN filled in, and of course has rights to the mailbox, you can impersonate the cross forest contact. That implies that you need to set the MayImpersonate right on the contact object in the AD. You do this via the Add-AdPermission cmdlet. Of course, since a cross-forest contact doesn't have his own mailbox in the database, there is no database to add the MayImpersonate right to. As a result, you have to set MayImpersonate on each cross-forest contact that you want to impersonate.
Hope that helps
------------------------------------
Reply:
When is it recommended to use one method rather than the other? For example, if you have a process that runs as a service and needs to access a few folders in many mailboxes is it recommended that you use impersonation or delgation?
------------------------------------
Reply:
There are no hard and fast rules for preferring one over the other. However, if you have a service account (not a real person) that needs to perform work on behalf of one or more accounts, I would suggest using Exchange Impersonation. I would NOT give EI rights to a normal user account. Remember, with EI, the actions are performed using the rights of the "Act As" account in the SOAP header, not the caller's (service account) rights. Another reason to use EI is that you can stamp the mailbox database with the MayImpersonate right so that the service account can impersonate all accounts in that mailbox database which is much easier to administer than giving delegate or send as rights on each mailbox.
In contrast, if a given user (real person) needs access to another mailbox account, I would suggest using delegation (if you want the 'John Smith on behalf of Jane Doe' or Send As if you want emails to appear as if they came from the mailbox owner.
------------------------------------
Documentation about Network Discovery + DHCP
Network discovery in ConfigMgr has now DHCP tab visible even ConfigMgr is running its services with LocalSystem.
The documentation about network discovery and DHCP tab is little bit confusing or misleading:
The documentation titled "About DHCP Servers and Network Discovery" says the following:
"When configuring Network Discovery to discover a client, you can set it to use DHCP servers to discover DHCP clients. Although this functionality is useful, it does have some limitations.
The primary limitation to using DHCP servers for the Network Discovery method is that the site server computer$ account must have user-level security access to the DHCP server specified on the DHCP tab of the Network Discovery Properties dialog box.
This means that one of the following conditions must be true:
- The specified server is the DHCP server of the Configuration Manager site server.
- The computer running Network Discovery and the DHCP server are in the same domain.
- The computer running Network Discovery and the DHCP server trust each other.
- The site server computer$ account has the same user name and password as a local computer account on the DHCP server.
- The site server computer$ account has the same user name and password as an account in the DHCP server's domain."
In my opinion, the only reasonable scenario using DHCP network discovery would be when site server and the DHCP server are in the same domain (or their domains trust each other), because then you can add site server's computer account to DHCP server's domain "DHCP Users" group.
In the list of following conditions, the bullet #1 is incorrect: you could do a DHCP discovery, even though site server is not a DHCP client.
Bullet #2: correct. However, what you mean by "the computer running Network Discovery"? Isn't the site server always doing the network discovery? So this "the computer running Network Discovery" should be "site server".
Bullet #3: if site server and DHCP server are in the same domain they trust each other. If they are in different domains and those domains trust each other, site server and DHCP server trust each other. I don't know a way, where I could define trust between computer accounts, if domains don't trust each other.
Bullet #4 & #5: Even though computer accounts have their own passwords, normally OS automatically changes this password within the domain and it is quite difficult to find out what is the actual computer account's password. I have never manually defined computer account's password. I suppose that you could
a) disable computer's automatic password mechanism at site server's and DHCP server's domain
b) export the hash of site server's computer account password from site server's domain and create a new computer account for site server to DHCP server's domain and finally import the hash of password to this new computer account
However, I don't think this would be a supported scenario and I definately wouldn't recommend this procedure.
Panu Saukko
Reply:
Hi, Panu,
Bullet one is not incorrect, it's just one possible scenario. The lead into the bullets states that
"one of the following conditions must be true", not that all of them are true.
For the rest, I agree that they aren't as clear and concise as they could be. I will file a bug to look at for a future doc update.
------------------------------------
Reply:
Would this sentence make sense:
"The primary limitation to using DHCP servers for the Network Discovery method is that the site server computer account must be a member of DHCP Users group in DHCP server specified on the DHCP tab of the Network Discovery Properties dialog box. This means that the site server and the DHCP server has to be in the same domain or DHCP Server's domain must trust site server's domain."
The key thing is the DHCP Users group membership and this requires the same domain or trust relationship. Site server can be a DHCP client to a DHCP server from untrusted domain and you cannot then add site server's computer account to DHCP server's DHCP Users group.
If the site server could list all DHCP leases from a DHCP server, which is in untrusted domain (thus the site server cannot be in DHCP Users group) just because site server is a DHCP client to this DHCP server, it would be a security bug in DHCP server's implentation.
Also the documentation should mention that DHCP server must be running Windows Server OS. I don't think ConfigMgr could get information e.g. from Linux based DHCP server.
------------------------------------
Reply:
------------------------------------
Reply:
------------------------------------
Software Deployment Adobe Professional 8
Hello,
So I have installed my SCE and it seems to be working fine. I can get all the reports I need, push down all the patches, and use all the remote tools. However I am unable to push down Adobe Professional 8 to two workstations in my network. Now I think this may be becuase of the way I am building the software package so if that is the case please correct me.
How I built the package was I copied the entire CD to a folder called AdobePro8 on the system. Then I started up the Create new Software package and deploy wizard. I selected the setup.exe and included the subfolders which make the file size around 483mb. After the package is done trying to convert / compress into a CAB for deployment I get the following error: The creation of your package has failed. Please ensure you have run The Feature Configuration Wizard, and that the package you are creating does not contain any single file larger than 500MB and try agian. From here I am unable to go any further.
Next I tried creating the package with just the setup.exe file without the subfolders. This created a successfull package and installed but it installed nothing on my workstation.
Next I tried creating the package with the AcroPro.msi and it created teh package successfully but when deploying it failed to install on the systems.
So I have tried everyway I can think of to deploy this package. Any help would be greatly apprciated.
Also on a side note could someone verify if I am understanding the Publish to Add/Remove option.
Here is how I belive it works:
If you Publish to Add/Remove this gives the user the option to install the package. (If this is how this works and the user has the choice how would the user go about installing it after it has been approved and published to Add/Remove if they have local admin rights on there computer)
If you DO NOT Publish to Add/Remove they are prompted to install the package at the time desginated either deadline or common update time.
Thanks.
Reply:
You might try following Jie-Feng Ren's directions regarding certificates at the bottom of this post:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2019331&SiteID=17 .
The way you initially went about creating your Installation should be correct, but since your total install size was less than 500mb I am guessing that no 1 file in the install was larger than that, so we are probably looking at another issue.
HTH,
Tim
------------------------------------
Reply:
Thanks for the post. Yeah i have tried Jie-Feng Ren's directions to add the WSUS certificates in the proper places. Still have the same problem. However I can deploy smaller packages just fine such as adobe reader ect.
------------------------------------
Reply:
Thanks for the post. Yeah i have tried Jie-Feng Ren's directions to add the WSUS certificates in the proper places. Still have the same problem. However I can deploy smaller packages just fine such as adobe reader ect.
------------------------------------
Reply:
I'd liek to suggest you capture screen shots of the related symptoms with "%programfiles%\update services\logfiles\softwareDistribution.log and send them to SCEDATA@microsoft.com
Note:
Please include the following three lines in the email body:
Software Deployment Adobe Professional 8
http://forums.microsoft.com/TechNet/ShowPost.aspx?postid=2284252&siteid=17
Eric Zhang - MSFT
-------------------- Regards, Eric Zhang Microsoft Online Community Support
------------------------------------
Reply:
As this thread has been quiet for a while we will be changing the issue type to 'Comment'.
If you wish to return to this question you can go ahead and change the type back to 'Question'. Then you can edit your initial post and change the radio button at the top of the post editor window.
If the issue has been resolved, we'd love to hear your solution. By sharing your experience you can help other community members facing similar problems.
Thanks!
-------------------- Regards, Eric Zhang Microsoft Online Community Support
------------------------------------
