SCCM 2007 OSD to add computer account to domain

Running SCCM 2007 R2 OSD to add computer account to domain has always been working, until recently after I added Intel 217/218 NIC drivers to the PE boot image.
The task sequence "Apply Network Settings" runs successfully though. It broke other TS steps too, such as enabling BitLocker, because, I guess, if the computer is not domain-joined, it won't be able to write recovery key to AD. I can use the same
network account to manually add the computer to domain. This doesn't seem to be a network issue, because the NIC drivers are applied, and software installation in the TS runs with no issue.
Here's the deployment log:
==============================[ OSDNetSettings.exe ]===========================
Command line: "osdnetsettings.exe" configure Setting %SystemRoot% to "D:\Windows"
Loading existing answer file "D:\Windows\panther\unattend\unattend.xml"
Configuring global network settings
Join type: 0 Joining domain: MyDomainName
Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "amd64"
DNS domain: DNS domain search order: IP filter sec enabled: false
No adapters found in environment.
Performing global configuration only.
Writing configuration information to D:\Windows\panther\unattend\unattend.xml
Successfully saved configuration information to D:\Windows\panther\unattend\unattend.xml
Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings
finished: 0x00000000
Thanks and regards.

Similar Messages

Add computer account

I'm trying to add a computer account in workgroup manager but everything is grayed out.
Yes, I'm authenticated (as diradmin)
If I try to add it with the network view, it says that I'm not authorized to perform the operation.
What should I do ?

It would help to know which directory you were attempting to add the computer account to -- you can't add it to /NetInfo/DefaultLocalNode as far as I know. It should have been greyed out in that case.
If you had the LDAP directory selected and were authenticated as diradmin, then Workgroup Manager should have allowed you to create a machine account.

Binding to OD (10.5.2) adds Computer accounts with client realm names

After applying “security Update 2008-002 v1.1 Server (leopard)” to a server running 10.5.2, clients were bumped from binding.
When I re-bind to OD, 2 new entries show up in computer accounts, one is the FQDN,( e.g., labtable6.physicslabs.uri.edu), the other is a Realm name (e.g. LKDC:SHA1.03344892C418CB16C250B59EAA7F93FEF79EF257.
Not only that, but in the list of principles in the Kerberos database, 2 entries for each machine are added to each service (e.g.,
afpserver/[email protected]
and
afpserver/LKDC:[email protected] ABS.URI.EDU.
Everything runs OK but I have to connect again to get AFP shares, but I cannot reconnect from the sidebar in finder, only from the Go menu, or a command.
All names in the DNS and Reverse IP lookups Resolve OK.
Has this happened to anyone else? I can fix the double entry in the computer accounts by just deleting the realm name, but I’m a bit worried about the double entry in the KDC.

Follow up
I used:
sso_util to remove the KDC on clients and
Kadmin to remove multiple entries in the KDC of the server.
Broke the bind (or whatever you call it) and bind again, no second entry in either Workgroup Manager’s Computer Accounts and no multiple service principles on the server’s KDC.
The following sight were helpful on this issue
http://forums.bombich.com/viewtopic.php?t=11834&highlight=lkdc
http://www.netmojo.ca/blog/2008/01/30/tiger-to-leopard-server-migration-part-fou r/
http://web.mit.edu/macdev/KfM/KerberosClients/KerberosApp/Documentation/using-os x.html#startup
I guess when I was installing Leopard LDAP I was using Tiger manuals and didn’t know about the “Back to My Mac” stuff.
My mistake:,the other issue with the finder sidebar is something different see:
http://discussions.apple.com/thread.jspa?messageID=5698233
Onward through the fog.

SCCM 2007 OSD - Windows XP to Windows 7 migration - Automatically install user applications

Hi all. I have been searching for this subject but haven't figured out the right search terms yet...what I want to do is:
We are doing an "in-place-upgrade" of all of our WinXP machines to Win7. It is really an "OS Refresh" process I guess. What I can't figure out is how to get SCCM to automatically install the extra user applications into Windows 7 after
XP has been replaced.
So for example, ComputerA has WinXP, our company standard base applications, and Acrobat Pro installed. I can deploy our "gold Win7 image" with SCCM, which includes the Win7 OS, and our company standard base applications. But how do I get SCCM
to recognize that Acrobat Pro was installed in XP, and to automatically install it after the Win7 install is complete? I just can't wrap my head around it.
The only way I could think of was to have a step at the beginning of my TS that audits the WinXP OS for installed applications before the HDD is wiped. For every application this step detects, it sets a TS Variable (ie: AcrobatInstalled=True). Then I have
to add a step for every possible application to the end of my TS that checks for the TS Variable, and installs the application if =True.
Is there an easier/better way? Is this something USMT or MDT can do (we have never used either)? thanks again for any help provided!

Wow thanks Jason, that is exactly what I was looking for, I just could not get the right Google search terms.
It does look like a lot of work to setup, but may be worth it. Out of curiosity, is this what you personally actually do for a large XP to Win7 migration for your clients? Or do you manually inventory your XP machines before the Win 7 install, and then manually
push the appropriate software after Win7 is installed?
We have been doing the second option for years on XP to XP refreshes, but human error during the manual inventory or manual push steps causes some inconvenience to our users. The completely automatic option would probably help, but appears to be much work
to setup and maintain. It also does not account for applications that are "installed" but do not appear in Add/Remove programs (ie: SQLDeveloper, etc).
But thanks so much for your help (again)!

SCCM 2007 R2: PXE Service Point Properties: Database Account

Got the following constellation:
Site Server: SRV01 (W2K8 / SCCM 2007 R2)
SQL Server: SRV02 (W2K8 / SQL 2008 )
Deploy Server: SRV03 (W2K8)
Basic Installation worked. Now I try to install DP and PXE Role on SRV03. All servers are member of each other's local admin group (all servers are running in one domain).
I installed WDS on SRV03. Everything's fine. After that I configured PXE role on SRV01 for SRV03 (configured nothing special in this area) WDS stopped on SRV03. After defining a PXE service point's computer account (a domain admin account that is also member of the local admin group of each server) in SCCM admin console on SRV01 for thePXE Role on SRV03 the WDS service on SRV03 able to start.
Looking at SQL Server during my tests I can see that the server account of SRV03 was properly added to the SMS DB with expected PSP_Role.
What is the reason that I'm not able to get the WDS service started on SRV03 without a special PXE service point account?
Thanks in advance for any idea.
Alex

I'm having the same issue, same kind of setup and error in my logs. I'm not able to kickstart the WDS Service of my DP with the computer account. However, if I use the ConfigMgr account it works without any problem. There is no indication that there is
an issue with the computer account's permissions.
I did activate Verbose logging on the DP and when trying to start WDS Service I get the following:
[1948] 19:51:28: WDS Diagnostics Initialized
[1948] 19:51:28: [Profiles] Initialized.
[1948] 19:51:28: [MCSCOPE] Address Range=239.0.0.1-239.0.0.254, Count=254
[1948] 19:51:28: [UDPPorts] Dynamic Port Range: 64001-65000.
[1948] 19:51:28: [RPC] Using Tcp Port 5040 for Rpc Calls.
[1948] 19:51:28: [RPC] Client Impersonation Logging=Disabled
[1948] 19:51:28: [RPC] Host Name: debobnbk02.emea.att.com
[1948] 19:51:28: [RPC] NTLM/Kerberos Spn: ldap/debobnbk02.emea.att.com
[1948] 19:51:28: [RPC] Initialized
[8920] 19:51:28: [RPC] Server Started.
[1948] 19:51:28: WDS VSS Writer Pre-Initialized
[1948] 19:51:28: [BINLSVC][RPC] Registered
[1948] 19:51:28: [BINLSVC] Provider Initialized.
[1948] 19:51:28: [218][WdsImgSrv] -> Initialize
[1948] 19:51:28: [249][WdsImgSrv] -> pInitializeManagement
[1948] 19:51:28: [327][WdsImgSrv] <- pInitializeManagement=c1030104
[1948] 19:51:28: [327][WdsImgSrv] <- Initialize=c1030104
[1948] 19:51:28: [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovider.cpp:147] Expression: , Win32 Error=3238199556
[1948] 19:51:28: [WdsImgSrv] Initialization Failed (rc=3238199556)
[1948] 19:51:28: [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovhdl.cpp:169] Expression: , Win32 Error=3238199556
[1948] 19:51:28: [WdsImgSrv] Deleted.
[1948] 19:51:29: [WDSMC][RPC][Ep=Registered
[1948] 19:51:29: [WDSMC][RPC][Ep=Registered
[1948] 19:51:29: [WDSMC] Provider Initialized.
[1948] 19:51:29: [1201][WDSPXE] -> CBannedGuids::Initialize
[1948] 19:51:29: [1201][WDSPXE] -> CBannedGuids::Shutdown
[1948] 19:51:29: [1201][WDSPXE] <- CBannedGuids::Shutdown=0
[1948] 19:51:29: [1201][WDSPXE] <- CBannedGuids::Initialize=0
[1948] 19:51:29: [1825][WDSPXE] [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\wdspxe\src\pxeprov.cpp:172] Expression: , Win32 Error=3661
[1948] 19:51:29: [1825][WDSPXE] [SMSPXE] Initialization failed (rc=3661)
[1948] 19:51:29: [1825][WDSPXE] [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\wdspxe\src\pxeprovhdl.cpp:481] Expression: , Win32 Error=3661
[1948] 19:51:29: [1825][WDSPXE] -> CBannedGuids::Shutdown
[1948] 19:51:29: [1825][WDSPXE] <- CBannedGuids::Shutdown=0
[1948] 19:51:29: [1825][WDSPXE] [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\wdspxe\src\pxeprovhdl.cpp:598] Expression: , Win32 Error=3661
[1948] 19:51:29: [1825][WDSPXE] [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\wdspxe\src\pxemain.cpp:201] Expression: , Win32 Error=3661
[1948] 19:51:29: [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovider.cpp:147] Expression: , Win32 Error=3661
[1948] 19:51:29: [WDSPXE] Initialization Failed (rc=3661)
[1948] 19:51:29: [1825][WDSPXE] -> CBannedGuids::Shutdown
[1948] 19:51:29: [1825][WDSPXE] <- CBannedGuids::Shutdown=0
[1948] 19:51:29: [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovhdl.cpp:169] Expression: , Win32 Error=3661
[1948] 19:51:29: [WDSPXE] Deleted.
[1948] 19:51:29: [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\server\src\wdsservice.cpp:177] Expression: , Win32 Error=3661
[1948] 19:51:29: [Udp] Listen Shutdown.
[8388] 19:51:29: [NetMon] Network Interface(s) Change Notification
[8920] 19:51:29: [RPC] Server terminated (rc=0)
[1948] 19:51:29: [RPC] Listen Stopped.
[1948] 19:51:29: [BINLSVC] Shutting down
[1948] 19:51:29: [BINLSVC][RPC] Closed
[1948] 19:51:29: -> CBannedGuids::Shutdown
[1948] 19:51:29: <- CBannedGuids::Shutdown=0
[1948] 19:51:29: -> CBannedGuids::Shutdown
[1948] 19:51:29: <- CBannedGuids::Shutdown=0
[1948] 19:51:29: [BINLSVC] Deleted.
[1948] 19:51:29: [WDSMC] Shutting down
[1948] 19:51:29: [WDSMC][RPC] Closed
[1948] 19:51:29: [WDSMC][RPC] Closed
[1948] 19:51:29: [WDSMC] Deleted.
[1948] 19:51:29: [d:\longhorn\base\ntsetup\opktools\wds\wdssrv\server\src\ifmonitor.cpp:174] Expression: , Return Value=1 (WSLE=10038)
[1948] 19:51:29: Timer Queue deleted successfully.
[1948] 19:51:29: WDS Vss Writer Shutdown
Doesn't really tell much, but if there is someone who can shed a light on this, or tell me in which direction I need to look...

2008 Failover cluster unable to create computer account

Hello,
I have created a 2008 R2 Failover cluster and I am trying to add a Fail over File server to this.
I get the dreaded
Cluster network name resource 'OfMaClusterFS' failed to create its associated computer object in domain 'xxx.domain' for the following reason: Unable to create computer account.
The text for the associated error code is: Access is denied.
Please work with your domain administrator to ensure that:
- The cluster identity 'OFMACLUSTER$' can create computer objects. By default all computer objects are created in the 'Computers' container; consult the domain administrator if this location has been changed.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity 'OFMACLUSTER$' has 'Full Control' permission to that computer object using the Active Directory Users and Computers tool.
I have created clusters frequently in the past, on my own Domains that I am a domain admin of. Now I am trying to make one on our larger corporate domain that I am not a domain admin of and get this error.
By default, domain users can not add computer accounts to our domain. I do however have an limited account that can add computers to the domain... but I have tried all the tricks I can think of to try and add the Network name to AD and no luck.#
I have tried running the cluster service with this account, but it is still trying to use the OFMACLUSTER$ identity to create the Network name. I have tried manually creating the network name using my limited account, but that doesn't work either,
same error. I don't have the ability to change permissions on the computer name I added for the network name to AD.
I have raised a ticket to our wintel team to try and get them to help, but they aren't exactly the most responsive bunch. I'm just wondering what the best way around this problem is if I am not a domain admin and I can't make the changes I need, or
what concise instructions I can give to the domain admins so that they can help me out without saying that it is a security breach etc.
I would appreciate any advice on this as it's now urgent and also something I will have to do in the future fairly regularly and don't want to get caught in the situation in the future.

Hi jogdial,
To create a cluster, the minimum permission is: Requires administrative permissions on the servers that will become cluster nodes. Also requires
Create Computer objects and Read All Properties permissions in the container that is used for computer accounts in the domain.
If you create the cluster name account (cluster name object) before creating the cluster—that is, prestage the account—you must give it the
Create Computer objects and Read All Properties permissions in the container that is used for computer accounts in the domain. You must also disable the account, and give
Full Control of it to the account that will be used by the administrator who installs the cluster.
The related KB:
Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory
http://technet.microsoft.com/en-us/library/cc731002(v=ws.10).aspx
More information:
How to Create a Cluster in a Restrictive Active Directory Environment
http://blogs.msdn.com/b/clustering/archive/2012/03/30/10289577.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Renaming offline computer account on AD as part of OSD

I am looking for an automated solution to a Windows 7 "rebuild" problem and here is the story:
We periodically have computer hard disk failures and the machines will be rebuilt on a new hard disk at the build center using the model-specific hardware "carcass". Once the hard disk is built, it will be sent over to the affected user and a field
engineer will swap the hard disks onsite and do the domain join work and anything else necessary so as to have the old computer name back.
To explain this further, say if the computer which had a hard disk failure is 123 (i.e. the computer name), we build a new Windows 7 machine on a new hard disk with the computer name as 123X. Once this machine is fully built, we need to delete the old 123
account from the AD and rename the newly built 123X to 123 (and do the domain re-join etc...).
However, the requirement is that the old 123 computer account should still stay in the domain for some time after the new machine is built (i.e. for data recovery/bit locker operations purposes if needed) which means we do not ideally want to delete the
old 123 computer account on the AD immediately, instead, we want to rename it as 123XY even though the old 123 computer is no longer physically active.
Is this technically possible? If so, can it be automated as part of SCCM OSD TS?
Hope I have not introduced too much of confusion. The problem has been reported by the build team and they have asked me to come up with an automated solution and I have tried to explain the problem above to the extent I have understood it. Currently what
they do is before deleting the computer account 123 from the AD, they back up its bitlocker recovery key information manually in order to use it later on should the need arise.
Thanks in advance.

Hi Garth,
Owing to the complexity it would have introduced into the build process to differently process new builds/rebuilds/hard disk replacement etc. we ended up ditching that option, instead went for a PowerShell scheduled task which runs every week and dumps the
bitlocker recovery info into a super-secret location :)
Below is the script if you are interested....
#Tweak the below line to point to the OU in your AD org where all the bitlockered computer objects reside
#It will run recursively against all sub-OUs.
$SearchBase = "ou=workstations,dc=contoso,dc=ad,dc=local";
#check if the output folder exists;Create it if it doesn't
If ((Test-Path -path "$(Split-Path $SCRIPT:MyInvocation.MyCommand.Path -parent)\Reports" -PathType Container) -eq $false) {
New-Item -path (Split-Path $SCRIPT:MyInvocation.MyCommand.Path -parent) -name 'Reports' -itemtype directory | Out-Null;
#set up the output csv name. An example output csv name will be BLR_15032015_Sunday.csv
$OutputCSV = "$(Split-Path $SCRIPT:MyInvocation.MyCommand.Path -parent)\Reports\BLR_$(Get-Date -format "ddMMyyyy")_$((Get-Date).DayOfWeek).csv"
Get-ADComputer -filter * -SearchBase $SearchBase -SearchScope Subtree -ResultSetSize $null -ErrorAction SilentlyContinue | Foreach-Object {
$Compname=$_.name;
Get-ADObject -Filter 'ObjectClass -eq "msFVE-RecoveryInformation"' -SearchBase $_.DistinguishedName -Properties created,name,msFVE-RecoveryPassword -ResultSetSize $null -ErrorAction SilentlyContinue |
Select-Object @{Name="Computer Name";Expression={$Compname}},
@{Name="Date Added";Expression={$_.created}},
@{Name="Password ID";Expression={$_.name -match '\{.+\}' | Out-Null;($matches[0]).Trim();}},
@{Name="Recovery Password";Expression={$_."msFVE-RecoveryPassword"}}
} | Sort-Object -Property @{Expression="Computer Name";Descending=$false},@{Expression="Date Added";Descending=$true} | Export-CSV -force -Path $OutputCSV -NoTypeInformation
Probably not what you would have been hoping for but it has worked really well for us in the last 6 months and there has never been a lost bitlocker key related incidence escalated by the customer as we always have the backup reports to go back to.
Apologies, it was impolite of me not to update this thread clarifying what I ended up doing.

I have one home computer and our household has 2 iphones. I am signed up on itunes and now my husband would like to have an account with itunes as well. Can there be two accounts for 2 users for itunes on one home computer? How do I add another account ?

I have one home computer and our household has 2 iphones. I am signed up on itunes and now my husband would like to have an account with itunes as well. Can there be two accounts for 2 users for itunes on one home computer? How do I add another account ?

Have a read here...
https://discussions.apple.com/message/18409815?ac_cid=ha
And See Here...
How to Use Multiple iDevices with One Computer

SCCM 2007: SQL Clúster Add new nodes

We've installed SCCM 2007 with SCCM DB in a clúster SQL with two nodes (Node1, Node2)
We're going to add two new nodes Nodes3 and Node4. After, we'll remove Node1 and Node2 from Clúster...
I see that SCCM has two site system created (Node1 and Node2) and I don't know if SCCM will add the new nodes automatically when I add the new nodes to the clúster..
Any problem with this??

I have never done it and remote SQL is not best practice anyways.
http://technet.microsoft.com/en-ca/library/bb735870.aspx
So...
http://www.enhansoft.com/

Upgrade to SCCM 2012 R2 Fails by ADD SQL ACCOUNT

Hello,
im Testing Today the Upgrade to R2.
in Step to Upgrade the Database I become an Error xxx\Compuertname not found to add SQL Account
My Server name is xxx.de\computername an not xxx\computername (netbiosname with dot and same with DNS Name) .
Have anywhere an Idea as Workaround for me ?

Microsoft support were no help...
I found a couple work arounds:
Move the database to the site server, do the upgrade, move the database back to the database server
Hack the DB:
create a login with a valid user account on the master DB on the SQL server
stop the sql server
Start SQL in single server mode
From an elevated cmd (Run as administrator), access the right folder where sqlservr.exe executable is located and execute below commands. Normally you will find it at “C:\Program Files\Microsoft SQL Server\MSSQL[InstanceName]\MSSQL\Binn”
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn>sqlservr.exe -m
start SSMS in DAC mode: start SSMS, cancel the connection to the server,click on the
Database Engine Query icon (to the right of the new query button),and put admin: in front of the server name
run the following:
select @@servername
GO
use master
GO
sp_configure 'allow updates', 1
GO
reconfigure with override
GO
then do this:
update
master.sys.server_principals
set master.sys.server_principals.name
= 'domain\servername$'
where master.sys.server_principals.name
= 'domain.com\dummyaccount'
restart the sql server
upgrade SCCM
keep in mind i am currently testing this solution to make sure it doesn't cause issues

SCCM 2007 R3 New DP , how to add to all existing packages

Hi
Is there a script which allows an SCCM 2007 R3 DP to be automatically added as a DP for all existing packages? I know this is easily done in 2012 with Powershell support or DP Groups, but was wondering how to automatically add a DP to all existing packages
in SCCM 2007 R3
Any help greatly appreciated!
Thanks
Max

This is easily done in 2007 also without any scripting by using the Copy Packages Wizard: http://technet.microsoft.com/en-us/library/bb693746.aspx
Jason | http://blog.configmgrftw.com | @jasonsandys

OSD: scripted upgrade SCCM 2007 to SCCM 2012 not working (first attempt)

Hi,
We created a package in SCCM 2007 to upgrade the sccm 2007 client on a vista machine to SCCM 2012.
What we did:
1.uninstall 2007 client
2.ccmclean.exe
3.install sccm 2012 client
4.trigger machine policy update
All works fine but the install. If we run the script a second time, install DOES work fine.
Error log of failed attempt, please advise:
Failed to download client files by BITS. Error 0x800704dd   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
Sending Fallback Status Point message to 'sccmserver.ourdomain', STATEID='309'.   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
Failed to get client version for sending messages to FSP. Error 0x8004100e   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
Params to send FSP message '5.0.7958.1000 Deployment Error 0x800704dd. Path http://sccmserver.ourdomain/SMS_DP_SMSPKG$/FLSD00002'   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
State message with TopicType 800 and TopicId {87CA732B-9d2D-4CD1-BD93-CA2CCD20D691} has been sent to the FSP   FSPStateMessage   16/05/2014 17:35:48   3872 (0x0F20)
Failed to download from DP 'http://sccmserver.ourdomain/SMS_DP_SMSPKG$/flsD00002', error 0x800704dd.   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
Enumerated all 1 local DP locations but none of them is good. Fallback to MP.   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
Using branch cache option.   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
Adding file 'HTTP://sccmserver.ourdomain:80/CCM_Client/i386/vcredist_x86.exe' to BITS job, saving as 'C:\Windows\ccmsetup\vcredist_x86.exe'.   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
Failed to download client files by BITS. Error 0x800704dd   ccmsetup   16/05/2014 17:35:48   3872 (0x0F20)
Jan Hoedt

Hi,
"Error code 4dd (hex) = 1245 = "The operation being requested was not performed because the user has not logged
on to the network. The specified service does not exist." This clearly implies some sort of account issue. Exactly how are you initiating the client agent setup?"
For more information:
http://social.technet.microsoft.com/Forums/en-US/2c80c8c4-06b5-431f-b732-470b7e531794/ccmsetup-failed-with-error-code-0x800704dd?forum=configmanagerdeployment
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How do you add another account onto the same computer that has itunes?

I want to add another account to my already existing account so that my dad can have his own music on the same computer with mine. can i do that? or should i just move all of my stuff to an another computer and just let him have the old one? i know this prolly sounds confusing but someone please tell me if i can do this!

See if this helps: Using Windows XP User Accounts
Creating a separate Windows User account for each person on your PC will give you completely separate libraries. Each account has it's own iTunes folder, Library and iTunes Music folder and you load it with CDs etc just as you did with your original one.

OSD: upgrade sccm 2007 (XP) client to 2012, then deploy TS

Hi,
We have some Windows XP machines in our SCCM 2007. They are discovered via AD in SCCM 2012.
Now we would like to upgrade their client to SCCM 2012 then deploy (available) a task sequence to it (Windows 7 install). This way users can choose whenever to upgrade to Windows 7.
My questions:
*When I right click an XP/SCCM 2007 client and choose upgrade, nothing happens. How can I troubleshoot/follow the upgrade?
*Should the task sequence (SCCM MDT) contain a particular step or can we use the same as a bare metal (PXE) deploy (we do not want to keep any data from the pc)?
Please advise,
J.
Jan Hoedt

Do I understand it correct, that you are trying a Client Push Installation? If so, then start with looking at the ccm.log on the server-side for errors. That log file contains all the information about the push action.
You should be able to use the same task sequence. Just check the deployment settings and the first action of the task sequence (make sure it restarts in WinPE).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

SCCM 2007 OSD to add computer account to domain

Similar Messages

Maybe you are looking for