jamitupya

You nailed it, SCCM pulls data from the systems management container in order to pick up boundary and site data. You will need to extend the schema if you wish to test further... its not that scary of a process though can break... i recommend before you extend, ensure that all your replication has completed successfully using: repadmin /replsummary or repadmin /showrepl sample below.... C:\Users\XXXXXXXXX>repadmin /replsummary Replication Summary Start Time: 2009-11-20 14:00:44 Beginning data collection for replication summary, this may take awhile: ....... Source DSA largest delta fails/total %% error DOMAIN1DC1 10m:43s 0 / 10 0 DOMAIN1DC2 08m:33s 0 / 10 0 SUBDOMAIN1DC1 11m:44s 0 / 14 0 SUBDOMAIN1DC2 10m:44s 0 / 8 0 Destination DSA largest delta fails/total %% error DOMAIN1DC1 08m:39s 0 / 14 0 DOMAIN1DC2 11m:52s 0 / 14 0 SUBDOMAIN1DC2 04m:30s 0 / 14 0 Experienced the following operational errors trying to retrieve replication info rmation: 58 - SUBDOMAIN1DC1.SUBDOMAIN1.DOMAIN.COM

Hi Guys, I got some code that i need to extend to include detection of vista windows 7 2008 etc and was wondering if anyone could give me some assistance. basically i need to add detection of windows vista and 7 and possibly w2k8+ ....any ideas...have nfi btw... looking at snippets atm trying to solve.... '========================================================================== 'Determine OS using WMI '========================================================================== Dim sWXPP, sW2KP, sW2KS, sW2KAS, sW2KDS, sW2K3S, sW2K3W, sW2K3E, sUnkOS, sWbemOpSys Dim oWbemServices Dim cOperatingSystems Dim oInstance sWXPP = "Microsoft Windows XP Professional" sW2KP = "Microsoft Windows 2000 Professional" sW2KS = "Microsoft Windows 2000 Server" sW2KAS = "Microsoft Windows 2000 Advanced Server" sW2KDS = "Microsoft Windows 2000 Datacenter Server" sW2K3S = "Microsoft(R) Windows(R) Server 2003, Standard Edition" sW2K3W = "Microsoft(R) Windows(R) Server 2003, Web Edition" sW2K3E = "Microsoft(R) Windows(R) Server 2003, Enterprise Edition" sUnkOS = "OS Unknown or NOT supported" Set oWbemServices = GetObject("winmgmts:") Set cOperatingSystems = oWbemServices.InstancesOf("Win32_OperatingSystem") On Error Resume Next For Each oInstance in cOperatingSystems sWbemOpSys = oInstance.Caption If sWbemOpSys = "" Then sWbemOpSys = sUnkOS End If Next Select Case sWbemOpSys Case sWXPP Case sW2KP Case sW2KS Case sW2KAS Case sW2KDS Case sW2K3S Case sW2K3W Case sW2K3E Case Else sContent = sFJImg & "<h3><center>OS Not Supported:" _ & "<br><br>" & sWbemOpSys & "</center></h3>" oDialogWindow.document.body.innerHTML = sContent WScript.Sleep 1000 oDialogWindow.Quit WScript.Quit End Select

I got that yesterday also, are you doing an unattend.xml file? i am receiving that error atm also and when i disable unattend package it goes through fine....maybe a syntax error in the SIM export.... looking into it now

activexp.vbs '*************************************************************** '*************************************************************** ON ERROR RESUME NEXT productKey = "PXRQ3-7VPMV-CQWXR-8Y4KX-RD786" 'blocked genericPK = "PXRQ3-7VPMV-CQWXR-8Y4KX-RD786" const seqNumber = "010-053298" 'part of PID, derived from genericPK actvProxyServer = "<insert proxy data>" 'replace with values appropriate actvProxyPort = "<insert proxy data>" 'to the customer environment For Each wpaObj In GetObject("winmgmts:{impersonationLevel=impersonate}"). InstancesOf ("win32_WindowsProductActivation") 'Set new Product Key if the current PID's 'Sequence Number matches the global PID (once only) If Mid(wpaObj.ProductID, 7, 10) = seqNumber Then WScript.Echo "Sequence Numbers match!" 'Sequence Numbers match: get new Product Key from database 'Get new Product Key from database" productKey = GetProductKey() WScript.Echo "Product Key: " & productKey 'Set new Product Key result = wpaObj.SetProductKey(productKey) WScript.Echo "SetProductKey() returned = " & result If err <> 0 Then WScript.Echo Err.Description, "0x" & Hex(Err.Number) Halt End If End If ' ProductKey check/set 'If not yet activated, set proxy and activate the machine If wpaObj.ActivationRequired <> 0 Then serverName = wpaObj.ServerName WScript.Echo "ActivationRequired for " & serverName 'Set proxy. First save existing proxy for later For Each proxyObj In GetObject("winmgmts:{impersonationLevel=impersonate}"). InstancesOf ("win32_Proxy") savedProxyServer = proxyObj.ProxyServer savedProxyPort = proxyObj.ProxyPortNumber WScript.Echo "Saved Proxy: " & savedProxyServer & ":" & savedProxyPort Next 'Set temporary activation proxy For Each proxyObj In GetObject("winmgmts:{impersonationLevel=impersonate}"). InstancesOf ("win32_Proxy") result = proxyObj.SetProxySetting(actvProxyServer,actvProxyPort) WScript.Echo "SetProxySetting() returned = " & result If err <> 0 Then WScript.Echo Err.Description,"0x" & Hex(Err.Number) Halt End If Next 'Activate Machine result = wpaObj.ActivateOnline() WScript.Echo "ActivateOnline Method() returned = "& result If err <> 0 Then WScript.Echo Err.Description, "0x" & Hex(Err.Number) ' do not halt - need to reset proxy End If 'Restore proxy to original setting For Each proxyObj In GetObject("winmgmts:{impersonationLevel=impersonate}"). InstancesOf ("win32_Proxy") result = proxyObj.SetProxySetting (savedProxyServer,savedProxyPort) WScript.Echo "SetProxySetting Method() = " & result If err <> 0 Then WScript.Echo Err.Description, "0x"& Hex(Err.Number) Halt End If Next End If Next

also, are your running SP2? i had this issue with a dism 3.0 created image and when updated to SP2 fixed the problem....

I have never done a migration as such and will test this out in lab in the near future..... after i whip out a walkthrough for NAP and a planning guide for dummies on Large Scale deployments.... my thoughts anyway... A thought out of the box would be: If you have a Trust in place from old to new AD, build a script to migrate the PC (about 15lines of vb code) then have that object dropped into a group linked to the collection in question. Then have the TS drop that group and run another script to add to your new AD and groups.... i do something similar atm 1. Build GOLD Image WIM 2. Deploy Gold Image.TS (Tier0 Tools install and Prep) (Installs updates, strips drivers, installs DirectX, IE8, etc) 2a. - Push image with Tier0 Tools 2b. - Push Installs for from SYSPRep.inf (Series of batch files and VBS) 3. Boots windows - Runs SYSPrep minisetup 3a. - Runs configured items. - Installs A/V - Basic Configuration of OS to environment - Adds to BUILD OU in AD - Sets reboot/startup apps (runs Stage1.vbs file) (adds PC to tier1 AD Group) - Reboots, runs tier1 app installs 3b. - Checks for IP Range and Site settings from AD. - Adds to Correct OU - Adds PC to tier2 Group - Runs Specific Tier2 collection scripts - Builds , configures, applies GPO. 4. Reboots Completed. Entirely ZTI. its possible but can get very complex. work with the KISS (keep is stupidly simple) principals first and you'll figure it out. If in doubt, im sure we can add some logic or assistance.

4005 i generally see as a permission denied. check that the NAA account has access to the directories trying to access, redo the ACL if needed and don't forget to make recursive

stoopid SAN admin nailed 26TB of DATA and spent last 2days recovering :S glad we use ESX and GeoClustering but jebus, what a scare :S next weeks national holiday here in japan so will hopefully get some basics whipped out then :-D what ever i get i'll post anyway

Hey Jean, Sorry mate, major issues over the weekend and someone blew away our 3 SAN's and ESX Clusters.... off line for a few days. will try and get you a guide asap

Hi Jean, since no-one has answered, i am unsure as we mostly use the cisco nap solution or other vendors. Give me a week and i'll have a read and see what i can come up with :-) Jammy

We have virtualized our front ends, consoles, the Central Servers and Regional Servers are Virtualized (esx) however all the DP,PXE,SUP etc are all on physical servers. We also use these servers as Storage and Printing services etc. Works well....

though it states they should be installed on the same machine we have experienced SIGNIFICANT performance issues with this configuration in the past when performing large scale rollout. I think this comes down to a "preference" model on how you'd like to proceed, we have built both models and hybrids and they all work well in a stable environment. our current rollout is Central Reporting (GlobalHQ) - 3x3Node SQLClusters Central (Regional HQ) - 2x3Node SQLClusters Primary (Country) - 3Node SQLCluster Primary (Sites 100+) - Onboard SQL Secondary (Sites >50) - Primary SQL We run large clusters ONLY as a redundancy factor... we backup Sites to the Country SQL DB (daily) then too the Regional SQL DBS (weekly) and up too the Central Site (monthly). Works well for us but had issues with bandwidth initially. things to consider: WSUS/SUP and PXE with remote DB can be very temperamental even now we need to rebuild secondary sites enough that we have had to create proper doco to support this. Consider your QoS/CoS on the LAN/WAN if using truly remote DB's Before you go down this route give it some serious thought as MS are a bit particular about their supporting these type of instances. There are NUMEROUS issues and HEADACHE's that come with this.... you really need a "sh!t hot"(GOOD) AD Admin, lots of little changes and designs to be applied. your SQL Admin needs to be on the ball also.... we are always with the SQL Team fixing little things here and there ...mainly in the reporting side. if your SQL is not contactable for a couple of minutes you *may* need to reboot servers and do lots of log digging. You should aggregate your windows logs also to make life a little easier when reporting issues. Anyway....food for thought :-)

Hi Jeaostro, That is generally how it is done in my experience. We found that trying to build the "lets call it duplicated redundancy" into each individual region we were far better of modifying our business processes to allow this kind of contingency. Given you can assign "fairly" granular controls over activities in SCCM this was easier than trying to resolve these issues on a grand scale. noting however that we had absolute governance over the entire environment so wasn't really an issue. We generally put our primary in the central administrative site and push out to SUP's, also note that reporting in this method needs to be built to return results to the reporting site. Will have a look through doco again and brush up see if we can't help a bit more on the tech side. Jammy

Anyweb may be able to fill in more on the WSUS/SUP side of things, i believe he would have more knowledge on SUP. Enjoy :-)

Yup, keep the same name as they have now.

Hi Jaeostro, i didn't really find any guides like this however my company is a MS Strategic Alliance partner globally and as such i did a design and asked them to check it out for me. i will give you a basic run down of our projects of our scalable design... easily modified from 10k to 250k the design covered: 1 Forrest 1 Root domain (internal.dns) 6 regional domains (apc.internal.dns) COUNTRY OU's (best suited our administrative processes) 1 Central Site for reporting (RPT) 6 Central sites for the global regions reporting to RPT (APC, USA, AME, EUR, SAM, PAC) then each regions central site had country base primary servers (AU1) reporting to regional then Locational Primary servers, then for sites we had Secondaries and Branch where required.. EXCEPTIONALLY COMPLEX and took maybe 3months to do basic design and validation prior to submitting. This system had to support 200K Users globally. We also included APP-V, WSUS, OSD, ETC and also OCS r2. Your basic design looks sounds.... just flesh it out in a workspace before commiting to early.... Is this the best solution? Central/Primary/secondary as i described above?. A total of computers in the whole company is about 10 000. And we also need to be able to deploy about 800 computes in the night so they can be ready for the next work day. When you plan this make sure you put alot of thoughts into the system roles and your network capabilities. The design work can be reasonably quickly whipped out however doing your validation and bandwidth allocations in relation to WSUS(SUP) and APPV Streaming can be a nightmare. From the Project management / Problem resolution side: Don't be too greedy or ambitious with your OSD overnighters. We found that 200 a night was a good number for us to deploy with a team of 2 onsite staffers (1 over night onsite, 1 early starter and fault fixer) Some of the primary sites will be administered by local IT persons, but we also need to be able to manage all the sites from the central site. We had the same requirement however this is difficult to achieve with the security side... permissions become quite convoluted after a while. Highly recommend putting serious thought into how you will administer this...this becomes a nightmare in large deployments. Also contemplate building an APPV package of the SCCM Console just some basic thoughts, feel free to throw me some questions if you need to... if you get stuck with your design let me know and maybe i can extract some design information from one of our designs that may be able to suit your requirements... enjoy.... Jammy

I've experienced this previously also, have you restarted the WDSServer service? (I'm sure you have tried but might as well ask) if you have, refresh your boot images on the PXE point... sometimes file might get hooked by the WDS Process

I believe if you set as a mandatory TS it wont prompt.

In SCCM Console: Goto: Computer Management -> Operating System Deployment ->Boot Images You should see the 2 Defaults, x86 and x64? Click Add Boot Image: then in the source select \\servername\SMS_<CODE>\OSD\Boot\i386\boot.wim Call it what ever you want (e.g.x86 windows PE boot enviroment for SCCM 1.0 EN-US) distribute it to your DP's and the PXE SP. Make sure if your testing you enable F8 as per this link Enjoy :-)

also check that the option for "Allow users to interact with this program" is NOT checked :-)

Yup, thats what we do with some of our components. we just copy a directory of tier0 software to like c:\local\ then after we prep the wim on the box it automatically kicks off a set of scripts to run c:\local\appname\install.cmd xcopy.exe \\SERVERNAME\SHARENAME\Applications\*.* C:\Local\Applications\ there are heaps of ways to achieve this startup but we utilize a series of scripts to kickoff the config process.

Hi All, i've been trying to figure this out for a while but keep failing totally and in utter dispair i need to ask how i can do this I want to deploy software through AD Groups linked to Collections in SCCM. Is there an easy way to do this, can somebody give me a basic run down on how this should occur? i want to learn it but it is just one elusive SOB at the moment :S Cheers

Hey Guys and Gals, i am wondering if anybody has a hostname change and reboot WITHOUT rebooting in between? thanks all Jammy