Hi! I am having some issues automating the installation of SQL server 2008 R2 on windows server 2008 R2. When I advertise a task sequence to the machine it works. But when I try the same steps as part of a server deployment it fail with the following error: This SQL Server 2008 R2 Setup operation requires administrator privileges. Access denied. To continue, run Setup with an account that has administrator privileges on this computer. The weird thing is that the user I am running the step with, using "Run this step with the following account", has administrative privileges. Its the same account that is used to make the machine a part of the correct domain and it is a member of the local administrator group. I have run a script that switches off the UAC. I am doing the install from a Run Command Line step because I need variables in my installation command line. I use the same command line, with the same variables, in both deployment and regular advertising. Anyone have an idea why this would work when you advertise a stand alone task sequence but not when you do exactly the same in deployment? Hope someone can help :)

I'd compare the SQL installation logfiles in both (working and non-working) cases.Torsten Meringer | http://www.mssccmfaq.de

The failed installation does not leave any log files. Meaning the installation does not start. In the smsts log the entry i pasted is the most interesting. Its followed by this message: Failed to run the action: Install SQL server 2008 R2. Unknown error (Error: 84C4001F; Source: Unknown)

Open the command propmt by "run as administrator" and give try.Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Hmm can you do this from a "Run Commandline" step in a task sequence? I am using the "Run this step as the following account" option with a variable that contains the same user that makes the machine a part of the domain. It works when I do it manually and it works when I just advertise the steps that installs the SQL server. Only time it does not work is when I do it from a deployment. I have also disabled UAC with a reg key entry.

Here is some more log from the failed installation: Getting linked token InstallSoftware 18.08.2011 15:38:04 1920 (0x0780) failed to get the token information InstallSoftware 18.08.2011 15:38:04 1920 (0x0780) Get RunAs private desktop SMSTS-86406\SMSTSDesktop InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Run command line under a user account InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Found the location for the package _SMSTSXXX005AD. The location is on \\XXXX.xxx.xxx\SMSPKGG$\XXX005AD\ InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) nPos != CCM::Utility::String::npos, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,253) InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Creating a connection to \\XXX.XXX.XXX\SMSPKGG$\XXX005AD\ with default account InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Connection request for "\\XXX.xXX.xXX\SMSPKGG$\XXX005AD" InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) No credentials available for connecting to "\\XXXX.xxxx.xxx\SMSPKGG$\XXX005AD". See whether the share has already been connected. InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Connecting to "\\XXX.XXX.XXXX\SMSPKGG$\XXX005AD" InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Successfully connected to "\\XXX.XXX.XXX\SMSPKGG$\XXX005AD" InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Resolved source to '\\XXX.XXXX.XXX\SMSPKGG$\XXX005AD' InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Command line for extension .exe is "%1" %* InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Set command line: Run command line InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Working dir '\\XXX.XXX.XXX\SMSPKGG$\VIS005AD' InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Executing command line: Run command line InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Create a process under given user token InstallSoftware 18.08.2011 15:38:05 1920 (0x0780) Process completed with exit code 2227437599 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Microsoft (R) SQL Server 2008 R2 Setup 10.50.1600.01 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Copyright (c) Microsoft Corporation. All rights reserved. InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) This SQL Server 2008 R2 Setup operation requires administrator privileges. Access denied. To continue, run Setup with an account that has administrator privileges on this computer. InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) An error occurred during the SQL Server 2008 R2 Setup operation. InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Error result: -2067529697 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Result facility code: 1220 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Result error code: 31 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) For more information, review SQL Server 2008 R2 Setup logs in your temp folder. InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Command line returned 2227437599 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Entering ReleaseSource() for \\XXX.XXX.XXX\SMSPKGG$\XXX005AD\ InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) reference count 1 for the source \\XXX.XXX.XXX\SMSPKGG$\XXX005AD\ before releasing InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Released the resolved source \\XXX.XXX.XXX\SMSPKGG$\XXX005AD\ InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Process completed with exit code 2227437599 TSManager 18.08.2011 15:38:08 1720 (0x06B8) !--------------------------------------------------------------------------------------------! TSManager 18.08.2011 15:38:08 1720 (0x06B8) Failed to run the action: Install SQL server 2008 R2. Unknown error (Error: 84C4001F; Source: Unknown) TSManager 18.08.2011 15:38:08 1720 (0x06B8)

Oh ok. Am not sure you have tried to run command prompt as local administrator as mentioned in the below blog? Also, not sure this will resolve the issue or not (: http://blogs.1e.com/index.php/2009/05/18/running-a-configmgr-task-sequence-command-line-as-a-specified-user/Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

This SQL Server 2008 R2 Setup operation requires administrator privileges. Access denied. To continue, run Setup with an account that has administrator privileges on this computer. InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) An error occurred during the SQL Server 2008 R2 Setup operation. InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Error result: -2067529697 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Result facility code: 1220 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Result error code: 31 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) For more information, review SQL Server 2008 R2 Setup logs in your temp folder. InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Command line returned 2227437599 InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Entering ReleaseSource() for \\XXX.XXX.XXX\SMSPKGG$\XXX005AD\ InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) reference count 1 for the source \\XXX.XXX.XXX\SMSPKGG$\XXX005AD\ before releasing InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Released the resolved source \\XXX.XXX.XXX\SMSPKGG$\XXX005AD\ InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Process completed with exit code 2227437599 TSManager 18.08.2011 15:38:08 1720 (0x06B8) !--------------------------------------------------------------------------------------------! TSManager 18.08.2011 15:38:08 1720 (0x06B8) Failed to run the action: Install SQL server 2008 R2. Unknown error (Error: 84C4001F; Source: Unknown) TSManager 18.08.2011 15:38:08 1720 (0x06B8) Hello - Also, the user account or service account used for the installation has the administrator access to the workstation? it's there in local administrators group?Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

The failed installation does not leave any log files [...] For more information, review SQL Server 2008 R2 Setup logs in your temp folder. InstallSoftware 18.08.2011 15:38:08 1920 (0x0780) Isn't that conflicting information? Have you double checked that folder?Torsten Meringer | http://www.mssccmfaq.de

"Isn't that conflicting information? Have you double checked that folder?" Yeah I have gone through %temp% and there is nothing. I have had my SQL guy look to see if there is any place that the installation could put this log but there is nothing. I have gone through c:\windows\temp and any other temp folder but no log is to be found anywhere. "Hello - Also, the user account or service account used for the installation has the administrator access to the workstation? it's there in local administrators group?" Yeah the account used to install SQL server is also used to put the machine in the domain. The account is my personal admin account and is domain admin and has all the rights needed, it is also a member of the local administrators group. The thing is that it works if I just advertise the steps of the task sequence that install the sql server. But if I use the EXACT same steps, same variables same everything, during deployment it fails..

Unfortunately, I don't have any other suggestions (: May be time to call CSS?Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Nevermind. I got it working by using the local system account. No need for Run As. My SQL guy said local system would not work so I blame this on him! ;)