anyweb

Note: This article is a copy of this post. There may be certain situations where you need to move the Operations Manager database (OperationsManager) from one SQL Server 2005-based computer to another, including the following: · The current server is experiencing hardware issues and is not considered reliable. · The OperationsManager database is collocated on the same server as the Root Management Server and you have decided to dedicate a SQL Server 2005 for the database to improve scalability and performance. · You need to move the database and log file to a different volume because of space or performance reasons. · The current server is leased and is due to expire soon. · New hardware standards have been developed and approved, and you must upgrade your SQL Server-based computer to the new hardware specification. SQL Server 2005 supports the ability to change the location of the data files and of the log files between SQL Server-based computers, between instances on the same SQL Server-based computer, and different volumes on the same SQL Server-based computer. For more information about using this function in SQL Server, see the SQL Server 2005 documentation at http://go.microsoft.com/fwlink/?LinkId=93787. The following section describes the procedures to move the Operations Manager database from one SQL Server-based computer to another. Before You Start Go through this checklist before moving the OperationsManager database. · Make a current backup of all databases, especially the master database, from their current location. · Verify you have system administrator permissions on both SQL Server-based computers. · Verify you have installed and configured the new SQL Server-based computer as the existing one. · Verify you know the name and current location of the Operations Manager database. · Stop the OpsMgr services (OpsMgr Config Service, OpsMgr SDK Service, and OpsMgr Health Service for Root Management Servers and OpsMgr Health Service for Management Servers) on the Management Servers in the Management Group before proceeding. · Backup the secure encryption key on the Root Management Server using the SecureStorageBackup.exe utility. · Stop SQL Service if you want to copy the .mdf and .idf files to a different location. Note: If the SDK account is “LocalSystem” on the original system, you need to add that account to the new system. Specify OperationsManager as the default database for that account. Detaching the Database Perform the following steps on the SQL Server-based computer currently hosting the OperationsManager database: 1. Open SQL Server Management Studio. 2. In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, and in the Authentication list, and then click Connect. 3. Right-click the OperationsManager database, point to Tasks, and then click Detach. Note: This menu is visible only if you are a member of the sysadmin fixed server role and the server to which you are connected is SQL Server 2005-based. 4. In the Detach Database dialog box, check the status of the database. To successfully detach a database, the Status should be The database is ready to be detached. Optionally, you can select to update statistics prior to the detach operation. 5. To terminate any existing connections from the database, click Clear. 6. Click OK. The database node for the detached database is removed from the Database folder. 7. Once the database has been detached, you can copy the OperationsManager.mdf and OperationsManager.ldf files to a destination directory on the new SQL Server-based computer. Note: The default location of the OperationsManager.mdf is Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Dataand the default location of the OperationsManager.ldf is Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG. Attaching the Database Perform the following steps on the SQL Server-based computer that will be hosting the OperationsManager database: 1. Open SQL Server Management Studio. 2. In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, in the Authentication list, and then click Connect. 3. Right-click the Databases folder, and then click Attach. Note: This menu is visible only if you are a member of the sysadmin fixed server role and the server to which you are connected is SQL Server 2005-based. 4. In the Attach Database dialog box, click Add to specify the database to be attached. 5. In the Local Database Files dialog box, select the disk drive were the database resides and expand the directory tree to find and select the OperationsManager.mdf file. 6. Click OK, and the database node for the attached database will appear when you refresh Object Explorer by clicking Refresh on the View menu. Update the Database Server Name on the Management Servers After you have successfully moved the OperationsManager database, update the Registry on each Management Server in that Management Group to reference the new SQL Server-based computer. 1. Log onto the Management Server with administrator permissions. 2. Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor. Note: Before editing the Registry, follow your site’s backup policies with regard to the registry. 3. Under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup, double-click the value DatabaseServerName, and then change the value to the hostname of the SQL Server-based computer now hosting the OperationsManager database. 4. Click OK. 5. Close the Registry Editor. 6. After you have completed this step on all Management Servers in the Management Group, restart the OpsMgr Config Service, OpsMgr SDK Service and OpsMgr Health Service on the Root Management Server and restart only the OpsMgr Health Service on the remaining Management Servers. Important: Do not start the OpsMgr Config Service and OpsMgr SDK Service on the Management Servers, as these services should only be running on the Root Management Server. . Update the dbo.MT_ManagementGroup table 1. On the Windows desktop, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio. 2. In the Connect to Server dialog box, in the Server Type list, select Database Engine; in the Server Name list, select the server and instance for your new Operations Manager database (for example, computer\INSTANCE1); in the Authentication list, select Windows Authentication; and then click Connect. 3. In the Object Explorer pane, expand Databases, expand OperationsManager, and then expand Tables. 4. Right-click dbo.MT_ManagementGroup, and then click Open Table. 5. In the results pane, scroll to the right to the column titled SQLServerName_<guid>. 6. In the first row, update the value to reflect the name of the new database server name, replacing the name of the old server. 7. Click File, and then click Exit. Setting ENABLE_BROKER Before you can run tasks and use the Discovery Wizard to install agents, you need to set the ENABLE_BROKER value: 1. Open SQL Server Management Studio. 2. In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, in the Authentication list, and then click Connect. 3. Click New Query. 4. In the query window, enter the following query: ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE 5. Click Execute. 6. Enter the following query: ALTER DATABASE OperationsManager SET ENABLE_BROKER 7. Click Execute. 8. Close SQL Server Management Studio. Note: Closing SQL Server Management Studio closes the connection to the database in single user mode. Depending on your configuration, you may have to manually kill any process that is connected to the database before completing the ALTER query below. 9. Open SQL Server Management Studio. 10. In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, in the Authentication list, and then click Connect. 11. Click New Query. 12. In the query window, enter the following query: ALTER DATABASE OperationsManager SET MULTI_USER 13. Click Execute. You can verify the setting for ENABLE_BROKER is set to 1 by using this SQL query: SELECT is_broker_enabled FROM sys.databases WHERE name=’OperationsManager’. Note: Before you can use discovery, you must restart the following services: OpsMgr SDK Service, OpsMgr Config Service, and OpsMgr Health Service. You may have to restart the following services: SQL Server and SQL Server Agent. Backup Custom Management Packs Perform the following steps to backup your custom Management Packs. 1. Log on to a Management Server with an account that is a member of the Operations Manager Administrators role for the Operation Manager 2007 Management Group. 2. In the Operations Console, click Administration. 3. In the Administration pane, click Management Packs. 4. In the Management Packs pane, right-click the Management Pack you want to export, and then click Export Management Pack. 5. In the Save As dialog box, type the path and file name for the Management Pack file, or click Browse to save the file to a different directory, and then click Save.

absolutely, we can help you with the technology when it comes to it

and in case you missed it heres how to Extend AD

well you could do this in a variety of ways but the first two that come to mind are using Collection variables and HTA (hyper text application) i'd recommend the collection variables way because it is much easier to implement now you are probably thinking how would this work, well you could have variable checking in the task sequence which checks what domain or site you are in and based on that does X actions cheers niall

so should I be using the Installer files directly from the Cu1 iso and forget about the 4.5 iso, i.e. I should use the ISO below cn_ct_nl_en_fr_de_it_ja_ko_pt_pp_es_application_virtualization_4.5_for_ts_cumulative_update_1_x86_cd_x15-51720 ?

great stuff, keep it up ! the application that you must stream should be created in App-V correct ?

hi Peter, do you deploy the App-v client using SCCM or another way

ah great stuff, it must have been a bad driver somewhere, glad it's working now

how are you intending to deploy the machines ? using wds, mdt, sccm or other ?

yeah feel free to create some mockups of the new logo, I already have a friend doing one up and he created the logos for the sister site http://linux-noob.com this is the image template and it must says windows-noob.com in big letters with the catch phrase showing you how to do IT plus some graphical element so get cracking

if the computer has not received the application yet, and it's applicable then it will receive it, it all depends on your advertisement settings, but utilising AD groups is a great way of controlling how computers get software in SCCM

According to The Register, Intel plans to deploy Windows 7 on its employee's computers. When asked at a Technology Summit with reporters and analysts in San Francisco whether the company would wait until service pack 1 to deploy Windows 7, Intel's EVP and chief sales and marketing officer Sean Maloney said, "This time I think we'll go faster." This is good news for Microsoft since Intel and many other companies skipped Vista. The company's top salesman also sympathized with those who passed on Vista. "There was an excuse not to deploy Vista, because - rightly or wrongly - people said 'wait for service pack X' or 'we don't like the compatibility issues." But this time, things may be different. Maloney said, "There are really good reasons for the business client in terms of security, power management - lots of good reasons why you'd go for it." more via > http://www.neowin.net/news/main/09/07/30/intel-will-deploy-windows-7-on-employees-computers

take a look at this post, does it help in any way ?

This document is for information technology (IT) implementers who have planned a Volume Activation deployment and are now ready to review and perform the procedures needed for that deployment. download it here

hi Jb can you post the solution to this please, it was one of the posts lost in the forum upgrade today cheers

Step 5. Target the Deploy Task to the collection you want to receive the updates Expand the Deployment Management Tasks node and right click, choose Refresh you will see that the task is targetted to the Blank for Staging collection which is an Empty collection, right click it the Deployment Management task and choose properties select your targetted XP collection click ok and apply Step 6. Monitor your XP machines and verify that they are receiving the Updates just before the deadline occurs, your XP machines should start receiving the new Update Policy and inform you finally, once the deadline has been reached the updates are installed automatically

Step 4. Deploy the selected updates right click the selected updates again and this time choose Deploy software updates give the Deployment Task a name for Deployment Template, choose the one that suits your environment select our Deployment Package go with the Default Choice of Download Software updates from the Internet select your language set the Schedule as below review the summary and close

Step 3. Using the Search folder, select the new updates Open our Windows XP All Updates search folder and sort by BulletinID as you can see there are a few updates released since our Deployment Package was last updated a month ago, and we need to select those new updates since MS09-026 which was the last update listed in our Deploymet Package (From June 2009) Right-click and choose Download Software Updates on the select a deployment package screen click on browse and select our All Windows XP Updates Deployment Package on the Download Location screen choose to download software updates from the internet select your chosen language and click Finish click next and close when prompted...

ok the new look is now here, so............... what do you think ?????

hi all, back in June 1st, I notified you all that the site would be changing look soon, and today I undertook that job. For those of you that are nostalgic here's a quick look at how it was so by now you've probably noticed that the forums look different, yup, they've been updated to the latest release of IPB software today, during the upgrade process I had some mysql issues and dropped the database, the side effect of that was that any posts in the last day or so and any new signups will have been removed, for that I apologise and hope you understand that this is a one man show pretty much, anyway, I've fixed the database issues (it was a mysql user GRANT issue, missing some permissions) and all seems good, still to do 1. get the portal working again (or the Front Page to you and me) 2. get windows-noob.com LOGO, VOLUNTEERS anyone ??? 3. verify posting works etc... i hope you will all like the change and enjoy the benefits it provides cheers niall

no it has nothing to do with the PXE filter for MDT, can you please check your System Status component logs in SCCM to see if there are any obvious problems, other than that are you creating the boot images as outlined in the Deploy Vista guide here ?

were there some errors in System Status component logs to alert you of the fact that your management point was broken ?

Introduction In this guide I will show you one way of updating your monthly updates released from Microsoft on the second Tuesday of every Month. Many different scenarios can be followed to deploy software updates. In this example, we will use a Software Updates Deployment Package called All Windows XP Updates to store the updates we want made available to our XP machines. We will create a new Deployment Management Task to deploy the new updates, and we will clean up our previous Deployment Management Tasks and remove any expired updates referenced in it by deleting them. As we are not using Update Lists in this guide we will not be concerned with reporting, but if you want to report on the status of your Updates, you should use Update Lists as Part of your Process. This Deployment Package had been created earlier when setting up the Software Update Point, but you can create a new one if you need to. We will use a Deployment Management task to start the deployment called All XP Updates. and as you can see from the screenshot above it contains some updates which are expired and this is noticeable because of the Grey Icon. We will also use our Windows XP All Updates search folder which is created with the following Search Folder Criteria Step 1. Run a Synchronisation. Expand your Software Updates node in configmgr, right click on Update Repository and choose Run Synchronisation. Answer Yes when prompted. You can verify that the synchronisation process has completed in the Site Status, Component Status, SMS_WSUS_SYNC_MANAGER log. Look for Message ID 6702 which is SMS WSUS Synchronization Done. Step 2. Check our Deployment Package To start off the monthly update process we need to first see what updates we currently have in our Deployment Package and remove any expired or superseded updates contained within. Expand your Software Updates node in configmgr, expand the Deployment Packages node and highlight the All Windows XP Updates Deployment Package. Expand the Software Updates node within so that you can see what updates we have, click on the Bulletin ID heading to sort our updates. Take note of the Expired or Superseded updates and highlight them and once done right click and choose Delete. You can press CTRL while selecting these updates and don't forget to scroll so you see all updates. We only want Green updates in our Deployment Package. Click ok when prompted about the Delete process click ok if prompted about Deployment can fail process, this is ok as we will be updating the Deployment Management Task. At this point we now have removed all the expired updates so only green 'good' updates are left, sort the updates by BulletinID again and take note of the most recent one, in our case that is MS09-026

is the firewall disabled on the xp client ? is the timezone the same as the server ? open task manager on the client, click 'show processes from all users' and then push the client out, do you then see ccmsetup.exe start ? remember that the client push installation account must have local administrative permissions on the client so for testing in a lab, a domain admin account would be good

cool, but please do test out application installation via RAP in SCCM