-
Posts
91 -
Joined
-
Last visited
-
Days Won
5
Posts posted by binarymime
-
-
This section of the log seems to indicate a problem due to the OSE service already being installed, likely due to the Microsoft viewer you already have installed. Can you remove the viewer, install office, and then reinstall the viewer? It doesn't hurt to try at any rate
2014/09/05 11:22:31:030::[1884] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE
2014/09/05 11:22:31:030::[1884] OSE service binary is detected at location: C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE
2014/09/05 11:22:31:030::[1884] OSE is avaliable at C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE
2014/09/05 11:22:31:030::[1884] This OSE has version: 11.0.5525.0000. Skip using this version of OSE because its version is too low.
2014/09/05 11:22:31:030::[1884] Running Source Engine process detected
2014/09/05 11:22:31:030::[1884] Running version: 11.0.5525.0000
2014/09/05 11:22:31:030::[1884] Error checking already running ose version. Error code 0x00000000
2014/09/05 11:22:31:030::[1884] Stopping running the problematic Source Engine process
2014/09/05 11:22:31:030::[1884] Error attaching to OSE, error 0x00000000
2014/09/05 11:23:46:565::[1884] Cannot start standalone OSE. from C:\Microsoft_Office_Standard_2013\standard.ww\ose.exe. Error code: 0x80070102
2014/09/05 11:23:46:565::[1884] Error:
Also try the following if the above does not work:
http://www.edugeek.net/forums/office-software/133245-re-installation-error.html
-
Experiencing an extremely frustrating problem.
ENVIRONMENT:
1 Primary Site Server / DP (Main Office)
40 DP's (Remote School Locations)
- Hosted on a file server VM
- Contains 3 partitions: C: (System), E: (Data), I: (PKG share)
OS: Server 2008 R2 (Primary Site Server and File Servers / DP's)
SCCM Version: SCCM 2012 R2
We recently upgrade to SCCM 2012 R2. I have confirmed that this has not caused the problem I am about to describe. The only other change that has occurred recently is that we configured all of our DP's at each of our 40 sites to be pull distribution points. While this seems to be working fine we are now seeing a whole bunch of 0 Byte alpha numeric folders with a 0 Byte amd64 subfolder. These folders seem to attach to the E: drive on all of our File server distribution points....for the life of me I cannot figure out why and this occurred as soon as we switched to pull distribution points. While this does not seem to be having an erroneous effect on our environment, it is annoying and somewhat disconcerting as I have not been able to ascertain what is causing it. Any SCCM admins out their ever encountered this?
Thanks
-
Hi Tim,
A few things here. Ensure that you have an x86 and x64 boot image configured and deployed, regardless of the architecture of the OS that you wish to deploy. Secondly, ensure that the boot images for both architectures have the network drivers for the respective model that you are imaging injected.
Are you hosting DHCP on the DP, or is DHCP coming from a different server?
Thanks
-
It seems as though the account you are using for the domainjoin has insufficient rights to join / update a computer object already present in AD as evidenced by the following line in your log:
11/14/2013 13:27:05:302 NetpMapGetLdapExtendedError: Parsed [0x5] from server extended error string: 00000005: SecErr: DSID-031A1190, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
If possible try using a different account that is a member of Domain Administrators for the domainjoin step and post back your results
Thanks
-
MS has now released CU2 for sccm 2012 which allows importing of 3.1 boot wims, albeit with some limitations, they must be serviced and customized externally from your SCCM environment
http://support.microsoft.com/KB/2854009
-
How did you make out
-
Te settings are in device manager of the vm guest not the host
-
ROFL!
-
I would never install SCCM roles on a DC of any flavor. How many clients are you looking to support in the branch office? I would create the RODC independently and then configure a Windows 7 client as a distribution point if you have the available HD space, can ensure the machine stays persistently connected, and that your client load is not that large.
-
-
Use the steps outlined here:
http://blog.coretech.dk/rja/post-sccm-2012-sp1-failure-to-update-boot-images/
Let me know how it goes
-
You bet, just make sure you run a supported version of SQL as a backend for the configmgr database, this can be found on sccm 2012 documentation online
-
I found that I needed to update the distribution points with the newly upgrade boot images (they are upgraded to Winpe4.0 as part of the SP1 install), after this they started working. The error you are seeing is usually due to corruption of the boot images or that they do not exist where they need to exist.
-
I see this behaviour anytime we deploy as little as 2 machines simultaneously that are both at some phase of a task sequence. Subsequently if we try to boot an additional machine via pxe i see the exact same issue as you have posted anove intol the load from the pror two Machines subsides. You may have another service generating traffic thats flooding your lan
-
Om going to make a guess on this:
If you want to boot to winpe via a vm on hyper-v you must add a legacy network adaptor to it throufh the settings on the vm, you must then make it the first boot device under the bios option in te settings of the vm
-
k, next can you post the netsetup.log file from the C:\windows\debug folder on the client having the issue. What method are you using for your domain join step in the task sequence? An answer file or a domain join step?
Thanks
-
I would be happy to.
What information in particular are you looking for?
Any particular batchfiles you would like to see. Quick count I have about 200+ for various products.
I also tried the TS idea you are describing and I have tried using WMIC commands in the past as well, however in my experience I find that WMI corrupts far to often and I don't rely on it unless I have to.
The beauty of SCUP based updating is that my installable and installed rules are always dependent on the existence and versions of files or registry keys, so you don't have to rely on intact WMI repository information
Since the installed versions of administrated software are only ever what we install we simply uninstall based on msi product code or reference the applications .exe uninstaller via a batchfile. This seems to work well.
-
First and foremost I'm going to pretext this with the following:
- I hate Java, I hate the security holes, the administrative headaches, and the fact that its updated more frequently than a stock price.
That said...the only way I have been able to get this to work is by using a batchfile to invoke an uninstall script. I have attached them. rename uninstall_java.txt to uninstall_java.bat and JRERemove.txt to JRERemove.vbs.
-
Also, i realise WSUS is handled upstream in your environment, however SCUP became the only solution in the end...im not sure what would be involved logistically in doing so, but we use WSUS integration with SCCM fully, for windows updates as well. It makes administration a lot easier
-
This was an issue that I strategized and debated for a long time and it still only exists in my head. This reply may get long...
First and foremost our School Division subscribes to the Enterprise CAL Suite. I say this only to illustrate to you why we use SCCM and why I needed to find an SCCM way of doing things.
I utilize a combination of Applications and SCUP, I will summarize the process below, if you want me to elaborate on any of the points just let me know.
FOR USER DRIVEN INSTALLATION AND UNINSTALLATION:
- All of our software is distributed via applications, i don't use supersedence of any kind, our applications are all distributed via custom batch files, one install batchfile, and one uninstall batchfile, the install batchfile is always configured to install the latest version, our uninstall batchfiles removes current and prior versions. This allows us to advertise applications to device collections and our staff are then able to install and uninstall advertised applications at will. My detection rules simply look for current and prior versions so that the uninstall routine if invoked manually will remove old versions. These rules are based on msi product code version when we can, otherwise its a file based detection based on exe file version.
- in essence this means that if a staff member uses software center to install an application it will always install the latest version, if they choose to uninstall, it will uninstall all current versions and prior versions.
- These same application installers are leveraged via a UDI task sequence that our fields techs use for deployment of images at any of our 43 rural schools and offices.
FOR UPDATES:
- I distribute a WSUS self signed cert for use by SCUP via a legacy package, we don't currently leverage our PKI as it is being rolled out for Wireless internet at the moment and we haven't had time to test and deploy leveraging it further, however I want to do this eventually.
- using iExpress I package all of the source files for the following apps into .exe files that i publish to WSUS via SCUP:
FirstClass
Flash
Reader
Shockwave
Chrome
Firefox
Java
- the complied .exe files run the uninstall script as the pre-exe and the install script as the post-exe. This ensures clean updates all around, for many of these updates i use taskill commands in the install and uninstall scripts to ensure the updates work correctly.
- For each of these updates I have created custom Installable and installed rules. The installable rules check for the apps existence and then check the version # via registry and file version rules where applicable, if the versions do not match the current release, then the update applies. The installed rule then just checks to ensure the latest version is installed.
- The updates are advertised and users can run them manually for up to a week at which time they automatically install if they have not been run previously.
SUMMARY:
- The above routine keeps my applications node clean, and allows me to publish and expire updates from the SCUP console. It has been working great so far.
-
1
-
-
Can you post the log?
-
Odd i'm trying the above command:
setup.exe /s /n /noeula /nofinish
Dedicated Quadro FX 600 pack, driver version 311.35 and I receive the following error:
Failed to run the action: Install Nvidia graphics. Incorrect function. (Error: 80070001) incorrect function
Any further suggestions
-
K so just to confirm, you have removed the sup role from your site server and you have removed the wsus role from the server as well from server manager? If so reboot the server, reinstall wsus and the wizard should reset back to step cancel out of the configuration wizard for wsus immediately and then install the sup role from sccm, it should install correctly from this point
-
I am trying to figure out how to extend our SCCM 2012 hardware inventory by way of configuration.mof
I would like to inventory the "boolean DataExecutionPrevention_Available;" from Win32_OperatingSystem as shown in the link below, so that we know which of our machines are NX-bit compliant. I am unable to figure out the information that I need to include in the configuration.mof file to add this functionality to our hardware inventory
http://msdn.microsoft.com/en-us/library/windows/desktop/aa394239(v=vs.85).aspx
Any help would be greatly appreciated.
Thanks
SMS_PROVIDERS in Configuration Manager Service Manager
in System Center Configuration Manager (Current Branch)
Posted
According to this guy Microsoft told him that this is now done by design. So apparently its nothing to wory about. If its any consolation i see the same thing in my environemnt as well.
http://www.networksteve.com/enterprise/topic.php/Upgraded_from_SCCM_2012_R2_to_SP1,_%22SMS_Providers%22_component_sho/?TopicId=103143&Posts=4
I think the thing that puzzles me though is that the component log is supposed to be here:
.\%ConfigMgrInstallDirectory%\logs\certificate.log
I cant find the log anywhere....which raises the question of whether or not Microsoft is entirely correct on this. Sounds like a misbehaving component to me
Thanks