Push-down Blackberry Application Wirelessly

Posted by Dede Nurmansyah on May 10, 2010
Various / No Comments

Q:
Help, my application not wirelessly pushed to Blackberry Device and I found many following entries in PLOC log file

[40000] (05/10 09:29:49.722):{0x3D0} SCS::RemoveAppDeliveryRequests - No App Delivery Requests purged for User id 25
[40000] (05/10 09:29:49.722):{0x3D0} RequestHandler::PollForMissingApps: Failed to RemoveAppDeliveryRequests.
[20000] (05/10 09:29:50.331):{0x3D0} Device info for hardwareID 0x84000e07 could not be found.
[40000] (05/10 09:29:50.347):{0x3D0} RequestHandler::PollForMissingApps: Completed Poll For Missing Apps, elapsed time 1 seconds.

A:

  • Have you shared C:\Program Files\Common Files\Research In Motion\ folder yet? If no, share that folder and set share permissions to Read-Only for everyone (Note: Do not grant any write access!!).
  • Have you indexed your apps yet? If no, run the following command from command prompt;  C:\Program Files\Common Files\Research In Motion\AppLoader\Loader.exe /index. After you run that command, make sure there are new files created inside your apps folder,  PkgDBCache.xml and specification.pkg

It’s seem your device.xml file is not updated. Open your “C:\Program Files\Common Files\Research In Motion\AppLoader\” and replace the existing files with this device.xml and this vendor.xml file.
Good luck!

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay
  • Reddit
  • RSS
  • StumbleUpon
  • Technorati
  • MySpace
  • Slashdot

Change Default Logon Domain Name in The Logon Screen

Posted by Dede Nurmansyah on March 18, 2010
How Do I?, Infrastructure, Operating System / No Comments

Q:
How do i change the default logon name on Windows logon screen?
defaultdomainname_1

A:
Open regedit, and modify the following key:
“HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultDomainName”
Change the value data to the desired domain name, for example FAKEDOM.

REFERENCES
Microsoft: KB555050

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay
  • Reddit
  • RSS
  • StumbleUpon
  • Technorati
  • MySpace
  • Slashdot

Tags:

Scanning “Zombie” User Account in Active Directory

Posted by Dede Nurmansyah on March 18, 2010
Infrastructure, Scripting / No Comments

Back few month ago, i was write simple script to scanning possibly “death” machine in Active Directory. Now i would like to share with you another similar script to scanning “zombie” user’s account. In my own words, Zombie account is an account which still exist – either enabled or disabled – in Active directory while the actual user is no longer exist in organization. The zombie account could associate to user account or service account. The present of zombie account in the system, could lead to serious security issue and IT administrator should not underestimate on outcome risk might cause of it.

Continue reading…

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay
  • Reddit
  • RSS
  • StumbleUpon
  • Technorati
  • MySpace
  • Slashdot

Tags: , ,

SQL Server Reporting Services Timeout

Posted by Dede Nurmansyah on January 08, 2010
Various / No Comments

Q:
MSSQL 2005 server always log below error message every time it’s reboot:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 1/8/2010
Time: 9:14:12 PM
User: N/A
Computer: FAKERPT01
Description:
The SQL Server Reporting Services (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Continue reading…

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay
  • Reddit
  • RSS
  • StumbleUpon
  • Technorati
  • MySpace
  • Slashdot

Scanning “Death” Machine in Active Directory

Posted by Dede Nurmansyah on December 26, 2009
Infrastructure, Scripting / 1 Comment

Recently, i was notice that numbers of computers inside of Computer OU in Active Directory larger than the actual “running” machine in the network. I believe, it’s happen because those computers – that no longer exist in the domain or network – was not deleted from Active Directory properly. The advantages of this situation are no one have idea which computer that no longer exist or removed from the network permanently. Scanning all those machines with ping test will not help either, because some of machine probably on remote location which disconnected temporary from the network. And don’t tell me to manually check it, one-by-one! :D

Continue reading…

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay
  • Reddit
  • RSS
  • StumbleUpon
  • Technorati
  • MySpace
  • Slashdot

Tags: , ,