Archive: Posts Tagged ‘clients’

SCCM 2012 | Now Available: Update 1610 for System Center Configuration Manager !!!!

Commentaires fermés novembre 25th, 2016

Hi Geeks,


It’s with a big pleasure that i present you all features of this news 1610 version !


•Windows 10 Upgrade Analytics integration allows you to assess and analyze device readiness and compatibility with Windows 10 to allow smoother upgrades.

•Office 365 Servicing Dashboard and app deployment to clients features help you to deploy Office 365 apps to clients as well as track Office 365 usage and update deployments.

•Software Updates Compliance Dashboard allows you to view the current compliance status of devices in your organization and quickly analyze the data to see which devices are at risk.

•Cloud Management Gateway provides a simpler way to manage Configuration Manager clients on the Internet. You can use the ConfigMgr console to deploy the service in Microsoft Azure and configure the supported roles to allow cloud management gateway traffic.

•Client Peer Cache is a new built-in solution in Configuration Manager that allows clients to share content with other clients directly from their local cache with monitoring and troubleshooting capabilities.

•Enhancements in Software Center including customizable branding in more dialogs, notifications of new software, improvements to the notification experience for high-impact task sequence deployments, and ability for users to request applications and view request history directly in Software Center.

•New remote control features including performance optimization for remote control sessions and keyboard translation.

This release also includes new features for customers using Configuration Manager connected with Microsoft Intune. Some of the new feature include:

  • New configuration item settings and improvements now only show settings that apply to the selected platform. We also added lots of new settings for Android (23), iOS (4), Mac (4), Windows 10 desktop and mobile (37), Windows 10 Team (7), Windows 8.1 (11), and Windows Phone 8.1 (3).
  • Lookout integration allows to check device’s compliance status based on its compliance with Lookout rules.
  • Request a sync from the admin console improvement allows you to request a policy sync on an enrolled mobile device from the Configuration Manager console.
  • Support for paid apps in Windows Store for Business allows you to add and deploy online-licensed paid apps in addition to the free apps in Windows Store for Business

Click HERE for more information

SCCM 2012 R2 | Cumulative Update 1 for the System Center 2012 R2 Configuration Manager clients for UNIX and Linux !!!

Commentaires fermés avril 30th, 2014

Hi to all,


Great news, a new Cumulative Update 1 for the System Center 2012 R2 Configuration Manager clients for UNIX and Linux is available !!!

Issues that are fixed by the CU1

UNIX and Linux clients

  • In some cases, Linux clients may not initialize while the Scxcm.log file grows quickly. Additionally, the following warning message is logged in the /var/opt/microsoft/scxcm.log file:
  • datetime Warning [scx.client.agents.InventoryAgentState:338:27298:140010010693376] Hardware Inventory endpoint Notify gained the policy lock, but the system is not yet ready. Retrying. LinuxUNIXClient 01.01.1601 00:00:00 2666765960 (0×9EF39E88)
  • After a client upgrade, the UNIX or Linux client does not send the new client version number to the server.
  • When you run the ccmexec –v command, a version number is displayed that is inconsistent with the client version number that is reported to the server.
  • The Universal Linux client does not install on Linux computers that use OpenSSL versions greater than 1.0.0 if the library file Libssl.so.1.0.0 does not exist. Additionally, you receive the following error message from the installation script
  • Checking Prerequisites…
    Running preinstall validator
    /tmp/ccm/preinstallvalidator: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
    Pre-Install validator failed. Please check the version of OpenSSL with CM installation requirements.
  • The client does not install on Linux computers that have an Athlon kernel.
  • In some cases, the client may not install on AIX-based computers. Additionally, you receive the following error message from the installation script:
  • Registering Providers…
    exec(): 0509-036 Cannot load program /opt/microsoft/omi/bin/omireg.bin because of the following errors:
    0509-150 Dependent module libomiclient.so could not be loaded.
    0509-022 Cannot load module libomiclient.so.
    0509-026 System error: A file or directory in the path name does not exist.
    An error occurred while registering providers.
  • If multiple Network Access accounts (NAAs) are configured, and if one or more of the accounts is invalid for the distribution point, software distribution to a UNIX or Linux client may not retrieve the package.
  • When the server sends a policy resync command to the UNIX or Linux client, the client may stop sending inventory to the server or stop processing software distribution. Additionally, the following warning message is logged in the /var/opt/microsoft/scxcm.log file
  • Info [scx.client.scheduler.IScheduledTrigger:256:51452:140230841011968] Loaded a one-shot trigger that has already completed. Trigger will not be fired again.
  • Hardware inventory does not return serial number properties for the PC BIOS class for UNIX-based and Linux-based computers.
  • Hardware inventory returns no data for the PC BIOS class for AIX-based computers.



style="display:inline-block;width:728px;height:90px"
data-ad-client="ca-pub-5394482248757140"
data-ad-slot="8215329516">

Managing System Center Configuration Manager clients in a workgroup !!!

Commentaires fermés mars 1st, 2010

Hi,

When managing SMS or SCCM clients that are in a workgroup, clients will need access to a WINS server the contains the proper entries for the SMS/SCCM site systems.  If a WINS is not available, as an alternative you can edit the LMHOSTS and HOSTS files on each client to allow for name resolution.

LMHOSTS file:

Add the SMS information to an LMHOSTS file, which you can copy to each client:

<IP Address> Siteserver             #PRE
<IP Address> « SMS_SLP        \0×1A » #PRE
<IP Address> « SMS_MP         \0×1A » #PRE
<IP Address> « SMS_NLB        \0×1A » #PRE (Only needed if the MP is load balanced)
# « 12345678901234567890″

Note: There must be 20 characters between the quotation marks for each entry.  The last line (# « 12345678901234567890″) is there to help make sure of that requirement and you can eliminate it in your actual LMHOSTS file.

If your clients need to assign to a secondary site, replace the SMS_MP with the following:

<IP Address of Secondary Site MP> « SMS_XXX        \0×1A » #PRE (XXX replace with site code)
# « 12345678901234567890″

HOSTS file:

Add the SMS information to an HOSTS file, which you can copy to each client.

<IP Address> siteserver.your.domain
<IP Address> MPservername.your.domain

Both the LMHOSTS and the HOSTS file can be found in the \windows\system32\drivers\etc directory.  LMHOSTS will be named LMHOSTS.sam so after editing the file you will need to remove the .sam extension.

Once that is completed, open a command prompt and run the following command:

nbtstat -R

This will load the LMHOSTS file.

Thanks a lot to Ellis George