Google Android 11 Go Edition is Available

Posted by Darenji
at Friday, September 11, 2020
Leave a comment!
Labels: , ,

Android 11 - Launch Apps 20 Percent Faster






Android 11 just launched this week for Pixel devices and phones from OnePlus, Xiaomi, Oppo, and Realme, and now Google has detailed its counterpart designed for low-powered devices: Android 11 (Go edition).

One of the biggest new features is that Android 11 (Go edition) is supposed to work on devices with 2GB of RAM or less — a bump up from Android 10 (Go edition), which was made for devices with less than 1.5GB of RAM. But don’t necessarily expect to upgrade your existing 2GB phone: Android 11 Go is only going to come out with new phones with that much memory, not earlier ones, Google tells The Verge.

Also, Google says it’s up to OEMs whether they want to put Android 11 Go on a device instead of Android 10 Go, contradicting what was suggested in a document obtained by XDA Developers back in July. Google wouldn’t provide any examples of devices that can get the update.

[+/-] Read More...
Read more »

 

Malaysia Fixed Deposit (FD) Rates – SEP 2020

Posted by Darenji
at Monday, September 07, 2020
Leave a comment!
Labels: , ,

Fixed Deposit (FD) Rates as of September 2020


 
Bank Effective Rate (% p.a.) Minimum Deposit Maximum Deposit Tenure Promotion Period
Affin Bank 
(eFD Online Promotion)		 2.40 (3 months)

2.50 (5 months)

2.48 (6 months)

 RM10,000 RM200,000 3 months

5 months

6 months

 28 Aug to 10 Sept 2020
Hong Leong Bank
(eFixed Deposit /  Deposit-i		 2.30 RM5,000 RM2 million 3 months 1 Sept to 31 Oct 2020
OCBC Bank
(Premier Deal)		 2.90 RM10,000 RM3 million 3 months 1 Apr to 31 Dec 2020
Public Bank
(Fixed Deposit / Term Deposit-i)		 2.08 (3 months)

2.28 (8 months)

 RM10,000 RM10 million 3 months

8 months

 12 Aug to 31 Oct 2020
Public Bank
(eFD via FPX Campaign)		 2.00 (1 month)

2.10 (2 months)

2.20 (3 months)

 RM5,000 RM2 million 1 month

2 months

3 months

 20 July to 30 Sept 2020
RHB Bank
(Term Deposit - Counter /
eTerm Deposit via FPX)		 2.45 RM10,000 Maximum FPX Transfers

6 months 5 Aug to 30 Sept 2020

[+/-] Read More...

 

Caught Exception at Azure AD Driver Initialization

Posted by Darenji
at Monday, September 07, 2020
Leave a comment!
Labels: , , ,

Identity Manager Azure Active Directory Driver - Caught Exception during Initialization


Situation


The following error is received when attempting to start the Azure AD driver.

DirXML: [11/30/18 11:46:33.46]: TRACE:  Azure AD_Azure: RESTSubscriptionShim.init()
DirXML: [11/30/18 11:46:33.46]: TRACE:  Azure AD: Caught exception during REST Channels initialization.
DirXML: [11/30/18 11:46:33.46]: TRACE:  Remote Loader: PublicationShim.init() returned:
DirXML: [11/30/18 11:46:33.46]: TRACE:  <nds dtdversion="4.x" ndsversion="8.x">
    <source>
        <product build="20171120_1044" instance="Azure AD" version="5.0.1.2">Identity Manager Driver for Azure AD and Office 365</product>
        <contact>NetIQ Corporation</contact>
    </source>
    <output>
        <status level="fatal" type="com.novell.nds.dirxml.driver.azure.StatusException"/>
    </output>
</nds>
DirXML: [11/30/18 11:46:33.46]: 
DirXML Log Event -------------------
    Driver  = \VAULT\novell\services\DriverSet\Azure AD
    Thread  = Publisher
    Level   = fatal
DirXML: [11/30/18 11:46:33.46]: 
DirXML Log Event -------------------
    Driver  = \VAULT\novell\services\DriverSet\Azure AD
    Thread  = Subscriber
    Level   = error
    Message = Fatal error returned from shim

Environment


  • Identity Manager Driver - Azure Active Directory version 5.0.1.2
  • Identity Manager 4.8.0


Resolution


The Application User password being used by the Identity Manager Azure Active Directory driver to authenticate into Azure Active Directory contained a special character in the password.   In this case a < character.


After removing the special character from the password, and saving the new application password for the application user on the driver properties, the driver was able to start successfully.

[+/-] Read More...

 

Active Directory to Identity Vault Group Synchronization is Limited to 5000 Members

Posted by Darenji
at Monday, September 07, 2020
Labels: , , ,

Situation

Active Directory Groups that contain more than 5000 members cannot be published / synchronized to Identity Vault via Identity Manager's Active Directory Driver. They are truncated to 5000 members during the Publisher Channel polling cycle.

However, migrating the Group into the Identity Vault will temporarily sync up the member lists but any subsequent modification of the group in Active Directory will cause the group to again be truncated to 5000 members in the Identity Vault.

Search:  Users members being lost from large groups 


Environment

  • Novell Identity Manager 4.8
  • Novell Identity Manager Driver- Active Directory Driver


Resolution

Under the Driver Parameters > Advanced Options, set Enable DirSync Incremental Values to Yes.   This allows the driver to query and synchronize only modified users in the group (users being added or removed from the group) instead of the whole group. 


Additional Information

This issue occurs due to a limitation in Microsoft's DirSync API. Microsoft Active Directory limits the number of values returned in response to DirSync LDAP queries to 5000 values. This is an Active Directory hard limit and is not dependent on the MaxValRange parameter of the Domain Controller's LDAP Policy (see ntdsutil.exe)


For Active Directory whose Forest and domain are operating at or after "Windows Server 2003" domain functional levels, implementation of the DIRSYNC_LDAP_INCREMENTAL_VALUES control resolves this issue. This control was implemented since Identity Manager 3.5 Active Directory Driver Patch 1 - 20070601, now replaced by the Identity Manager 3.5.1 or later downloads.


The Incremental Values server control allows the Active Directory driver to ask for (and receive) only changed values of an attribute such as the member attribute on a group object preventing the need to continually sync the entire member list and hit the 5000 value DirSync limitation.


This parameter is already included in current versions of the Active Directory driver configuration (3.6 and higher)


<definition display-name="Enable DirSync Incremental Values" hide="false" id="115" name="enable-incremental-values" type="enum">

<description>Ordinarily the publisher will receive all member values of a group when one or more has changed. This option reports only the added or deleted member values during the poll interval. Requires 2003 Forest functional mode.</description>

<enum-choice display-name="Yes">yes</enum-choice>

<enum-choice display-name="No">no</enum-choice>

<value>yes</value>

</definition>

[+/-] Read More...

 

Subscribe to: Posts (Atom)